Commit 2d58f4f50fe07bd9688178ab6bed85bf20adbb63
1 parent
1f4818fe
Exists in
master
Should we erase the issue once it's fixed or recognized it as such in here?
Showing
1 changed file
with
3 additions
and
0 deletions
Show diff stats
Docs/DustemWrap_development_issues.txt
| @@ -9,3 +9,6 @@ | @@ -9,3 +9,6 @@ | ||
| 9 | - JPB, April 8th 2022: | 9 | - JPB, April 8th 2022: |
| 10 | Dustemwrap causes the Fortran to crash if the chrg keyword is not specified in the initial GRAIN.DAT file, but is subsequently added by the (*!dustem_params).grains[0].TYPE_KEYWORDS. A similar error is likely to occur for the spin keyword (untested). | 10 | Dustemwrap causes the Fortran to crash if the chrg keyword is not specified in the initial GRAIN.DAT file, but is subsequently added by the (*!dustem_params).grains[0].TYPE_KEYWORDS. A similar error is likely to occur for the spin keyword (untested). |
| 11 | We must force these pointers to not be empty just after writing our own GRAIN.DAT in /tmp, in the same way this is done in dustem_init.pro with the GRAIN.DAT from the fortran directory. | 11 | We must force these pointers to not be empty just after writing our own GRAIN.DAT in /tmp, in the same way this is done in dustem_init.pro with the GRAIN.DAT from the fortran directory. |
| 12 | +- *FOLLOW UP*: IC, May 15th 2022: A SOLUTION HAS BEEN IMPLEMENTED BY INTRODUCING the 'kwords' | ||
| 13 | +;keyword and specifying the necessary population keywords. IE: kwords=['plaw-ed-chrg-spin'] for the first grain population | ||
| 14 | +;to enable the use of spinning dust. THIS IS NOT AN ISSUE ANYMORE. | ||
| 12 | \ No newline at end of file | 15 | \ No newline at end of file |