From 2d58f4f50fe07bd9688178ab6bed85bf20adbb63 Mon Sep 17 00:00:00 2001 From: Ilyes Choubani Date: Sun, 15 May 2022 13:49:39 +0200 Subject: [PATCH] Should we erase the issue once it's fixed or recognized it as such in here? --- Docs/DustemWrap_development_issues.txt | 3 +++ 1 file changed, 3 insertions(+), 0 deletions(-) diff --git a/Docs/DustemWrap_development_issues.txt b/Docs/DustemWrap_development_issues.txt index d4ae31b..86e9a21 100644 --- a/Docs/DustemWrap_development_issues.txt +++ b/Docs/DustemWrap_development_issues.txt @@ -9,3 +9,6 @@ - JPB, April 8th 2022: 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). 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. +- *FOLLOW UP*: IC, May 15th 2022: A SOLUTION HAS BEEN IMPLEMENTED BY INTRODUCING the 'kwords' +;keyword and specifying the necessary population keywords. IE: kwords=['plaw-ed-chrg-spin'] for the first grain population +;to enable the use of spinning dust. THIS IS NOT AN ISSUE ANYMORE. \ No newline at end of file -- libgit2 0.21.2