Commit f183c015bb91ef80d56b995d1c3b9929ad330206
1 parent
70c02906
Exists in
master
formatting
Showing
1 changed file
with
6 additions
and
5 deletions
Show diff stats
Docs/DustemWrap_development_issues.txt
| 1 | -%This is a note containing development issues for Dustem | 1 | +%This is a note describing known current development issues for Dustem |
| 2 | %This file is called DustemWrap_development_issues.txt and is managed by J.-Ph. Bernard and Ilyes Choubani | 2 | %This file is called DustemWrap_development_issues.txt and is managed by J.-Ph. Bernard and Ilyes Choubani |
| 3 | -%Issues must be described as explicitely as possible | ||
| 4 | -%These issues must be checked before releasing Dustem and Dustemwrap | 3 | +%Issues must be described as explicitly as possible |
| 4 | +%These issues must be checked before the next joint release of Dustem and Dustemwrap | ||
| 5 | 5 | ||
| 6 | - JPB, April 8th 2022: | 6 | - JPB, April 8th 2022: |
| 7 | Dustem has a bug due to calculation accuracy for the THEMIS model, which solves by replacing max size values in GRAIN_THEMIS.DAT from 9.00E-6 into 8.99E-05 | 7 | Dustem has a bug due to calculation accuracy for the THEMIS model, which solves by replacing max size values in GRAIN_THEMIS.DAT from 9.00E-6 into 8.99E-05 |
| 8 | + | ||
| 8 | - JPB, April 8th 2022: | 9 | - JPB, April 8th 2022: |
| 9 | - Dustemwrap plante le Fortran quand le keyword chrg (et probablement aussi spin) ne figurent pas dans le GRAIN.DAT de depart (du Fortran) et sont rajoutés ensuite via (*!dustem_params).grains[0].TYPE_KEYWORDS | ||
| 10 | - We must force those pointers to not be empty just after writing our own GRAIN.DAT in /tmp, in the same qway this is don in dustem_init.pro with the GRAIN.DAT from the fortran directory. | ||
| 11 | \ No newline at end of file | 10 | \ No newline at end of file |
| 11 | + 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). | ||
| 12 | + 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. |