|
|
|
|
|
*_Format:*_ The hot fix should give the file and line to be edited, or a link to the patch with the correction. If the bug affects any predictions this should be noted. The date that the hot fix was posted should be listed, along with an acknowledgment to the person who identified the problem.
|
|
*Format:* The hotfix should give the file and line to be edited or a link to the patch with the correction. If the bug affects any predictions this should be noted. The date that the hotfix was posted should be listed, along with an acknowledgment to the person who identified the problem.
|
|
|
|
|
|
----
|
|
----
|
|
|
|
|
|
|
|
|
|
## Hot fixes to version C07.02.02
|
|
## Hotfixes to version C07.02.02
|
|
|
|
|
|
[ftp://gradj.pa.uky.edu/gary/cloudy_gold/hotfixes/patch4 patch4 (Unix patch)]
|
|
[Unix patch](http://data.nublado.org/cloudy_releases/c07_02/hotfixes/)
|
|
|
|
|
|
The code for testing convergence of an iteration was not safe against FP overflow, which could lead to spurious crashes. Place the patch file patch4 in the source directory and apply the patch, as described on the PatchFiles page to resolve this problem. Thanks to Linda Strubbe for reporting this problem. 2008 July 9.
|
|
The code for testing convergence of an iteration was not safe against FP overflow, which could lead to spurious crashes. Place the patch file patch4 in the source directory and apply the patch, as described on the PatchFiles page to resolve this problem. Thanks to Linda Strubbe for reporting this problem. 2008 July 9.
|
|
|
|
|
|
----
|
|
----
|
|
|
|
|
|
|
|
|
|
## Hot fixes to version C07.02.01
|
|
## Hotfixes to version C07.02.01
|
|
|
|
|
|
These have been included in the C07.02.02 service release.
|
|
These have been included in the C07.02.02 service release.
|
|
|
|
|
... | @@ -33,8 +33,8 @@ Only the penultimate line is changed: add SDIV right after the division sign. Th |
... | @@ -33,8 +33,8 @@ Only the penultimate line is changed: add SDIV right after the division sign. Th |
|
|
|
|
|
----
|
|
----
|
|
|
|
|
|
The __'rate coefficient for the reaction H^0^ + He^+^ -> H^+^ + He^0^ was incorrectly
|
|
The **rate coefficient for the reaction H^0^ + He^+^ -> H^+^ + He^0^ was incorrectly
|
|
entered__' as the reverse process. To fix edit the file atmdat_char_tran.cpp and change line 98 from this
|
|
entered** as the reverse process. To fix edit the file atmdat_char_tran.cpp and change line 98 from this
|
|
|
|
|
|
```
|
|
```
|
|
atmdat.HCharExcIonOf[ipHELIUM][0] += 7.47e-15*pow(phycon.te/1e4,2.06)*
|
|
atmdat.HCharExcIonOf[ipHELIUM][0] += 7.47e-15*pow(phycon.te/1e4,2.06)*
|
... | @@ -52,8 +52,8 @@ the source of the error. 2008 March 22. |
... | @@ -52,8 +52,8 @@ the source of the error. 2008 March 22. |
|
|
|
|
|
----
|
|
----
|
|
|
|
|
|
The __'code could fail with internal insanity when the interpolate option is used to set the
|
|
The ##code could fail with internal insanity when the interpolate option is used to set the
|
|
continuum shape in a series of calculations done in a grid__'.
|
|
continuum shape in a series of calculations done in a grid##.
|
|
Edit the file parse_interp.cpp and change line 415 from this
|
|
Edit the file parse_interp.cpp and change line 415 from this
|
|
|
|
|
|
```
|
|
```
|
... | @@ -73,7 +73,7 @@ for fixing it. 08 March 22. |
... | @@ -73,7 +73,7 @@ for fixing it. 08 March 22. |
|
|
|
|
|
----
|
|
----
|
|
|
|
|
|
The *_code could fail with internal insanity if the resolution of the continuum mesh, as defined in continuum_mesh.dat is made very fine*_. This is caused by round off error in the floating point numbers. If you need to use a very fine continuum mesh and encounter this problem you should make this fix. Edit routine cont_setintensity.cpp and change the code at line 201 to read as follows:
|
|
The *_code could fail with internal insanity if the resolution of the continuum mesh, as defined in continuum_mesh.dat is made very fine*_. This is caused by a round-off error in the floating-point numbers. If you need to use a very fine continuum mesh and encounter this problem you should make this fix. Edit routine cont_setintensity.cpp and change the code at line 201 to read as follows:
|
|
|
|
|
|
```
|
|
```
|
|
rfield.anu[i] = (float)(amean2/amean);
|
|
rfield.anu[i] = (float)(amean2/amean);
|
... | @@ -87,7 +87,7 @@ The *_code could fail with internal insanity if the resolution of the continuum |
... | @@ -87,7 +87,7 @@ The *_code could fail with internal insanity if the resolution of the continuum |
|
rfield.anu2[i] = (float)(amean3/amean);
|
|
rfield.anu2[i] = (float)(amean3/amean);
|
|
```
|
|
```
|
|
|
|
|
|
The first and last line are not changed - the if block is the patch code. This fix is only necessary if a very high resolution continuum mesh is to be used. Thanks to Valentina Luridiana for reporting this problem. 2008 Jan 23.
|
|
The first and last lines are not changed - the if block is the patch code. This fix is only necessary if a very high-resolution continuum mesh is to be used. Thanks to Valentina Luridiana for reporting this problem. 2008 Jan 23.
|
|
|
|
|
|
----
|
|
----
|
|
|
|
|
... | @@ -143,7 +143,7 @@ blr_rnfb.out: ChkAssert botch>>H 1 1.875m 0.5187 = 0.4040 -0.284 0.0 |
... | @@ -143,7 +143,7 @@ blr_rnfb.out: ChkAssert botch>>H 1 1.875m 0.5187 = 0.4040 -0.284 0.0 |
|
|
|
|
|
----
|
|
----
|
|
|
|
|
|
The *_set atomic data As oxygen 2 new did not select the Zeippen 1987 results*_. To correct, edit parse_set.cpp and change line 112 so that it reads as follows:
|
|
The *set atomic data As oxygen 2 new did not select the Zeippen 1987 results*. To correct, edit parse_set.cpp and change line 112 so that it reads as follows:
|
|
|
|
|
|
```
|
|
```
|
|
dense.lgAsChoose[nelem][ion-1] = true;
|
|
dense.lgAsChoose[nelem][ion-1] = true;
|
... | @@ -153,7 +153,7 @@ That is, change [ion] to [ion-1]. Many thanks to R. Surendiranath for uncoverin |
... | @@ -153,7 +153,7 @@ That is, change [ion] to [ion-1]. Many thanks to R. Surendiranath for uncoverin |
|
|
|
|
|
----
|
|
----
|
|
|
|
|
|
In *_FITS files produced for use in XSPEC*_, logarithmic interpolation was specified. This caused *_problems for negative values*_ since the log of a negative number is undefined. Ideally, there would be a command-line option to specify the interpolation method, but for now we just switch the hard-wired specification to linear interpolation. The effect is, of course, negligible for a sufficiently resolved grid with positive parameter values. Line 75 of grid_xspec.cpp should be changed from this
|
|
In *FITS files produced for use in XSPEC*, logarithmic interpolation was specified. This caused *_problems for negative values*_ since the log of a negative number is undefined. Ideally, there would be a command-line option to specify the interpolation method, but for now, we just switch the hard-wired specification to linear interpolation. The effect is, of course, negligible for a sufficiently resolved grid with positive parameter values. Line 75 of grid_xspec.cpp should be changed from this
|
|
grid.paramMethods[i] = 1;
|
|
grid.paramMethods[i] = 1;
|
|
to this
|
|
to this
|
|
grid.paramMethods[i] = 0;
|
|
grid.paramMethods[i] = 0;
|
... | @@ -162,13 +162,13 @@ Thanks to Bryan Armentrout for pointing out this issue. 2007 Sep 4. |
... | @@ -162,13 +162,13 @@ Thanks to Bryan Armentrout for pointing out this issue. 2007 Sep 4. |
|
|
|
|
|
----
|
|
----
|
|
|
|
|
|
[ftp://gradj.pa.uky.edu/gary/cloudy_gold/hotfixes/patch3 patch3 (Unix patch)]
|
|
[Unix patch](http://data.nublado.org/cloudy_releases/c07_02/hotfixes/)
|
|
|
|
|
|
*_Only one punch opacity command can be used in a given input stream*_ since all flavors of the punch opacity commands use the same variables. The fix involves several changes to the source and is included in R1286 of the C07.02 branch. It will be included in the next service release. Or place the patch file patch3 in the source directory and apply the patch, as described on the PatchFiles page. Thanks to Orly Gnat for reporting this problem. 2007 July 20.
|
|
*Only one punch opacity command can be used in a given input stream*_ since all flavors of the punch opacity commands use the same variables. The fix involves several changes to the source and is included in R1286 of the C07.02 branch. It will be included in the next service release. Or place the patch file patch3 in the source directory and apply the patch, as described on the PatchFiles page. Thanks to Orly Gnat for reporting this problem. 2007 July 20.
|
|
|
|
|
|
-----
|
|
-----
|
|
|
|
|
|
[ftp://gradj.pa.uky.edu/gary/cloudy_gold/hotfixes/patch2 patch2 (Unix patch)]
|
|
[Unix patch](http://data.nublado.org/cloudy_releases/c07_02/hotfixes/)
|
|
|
|
|
|
Thomas Rauch has recently *_updated his hydrogen-only grid*_. The test in the auto test suite was still based on the previous version of the grid. Using the *_new grid with the existing test case will yield botched asserts*_. This is not a problem in the code, but simply reflects the fact that we were still testing the older grid. In order to fix the botched asserts, change the following asserts in the file stars_rauch_hydr.in:
|
|
Thomas Rauch has recently *_updated his hydrogen-only grid*_. The test in the auto test suite was still based on the previous version of the grid. Using the *_new grid with the existing test case will yield botched asserts*_. This is not a problem in the code, but simply reflects the fact that we were still testing the older grid. In order to fix the botched asserts, change the following asserts in the file stars_rauch_hydr.in:
|
|
|
|
|
... | @@ -187,7 +187,7 @@ assert ionization Phosphorus element 6 -0.9347 |
... | @@ -187,7 +187,7 @@ assert ionization Phosphorus element 6 -0.9347 |
|
assert ionization Phosphorus element 7 -2.2680
|
|
assert ionization Phosphorus element 7 -2.2680
|
|
```
|
|
```
|
|
|
|
|
|
Alternatively you can apply the patch listed above using the Unix patch command. Download the file patch2 anywhere on your computer, then cd to the Cloudy tsuite/auto directory and issue the command *patch < /path/to/patch2*. You can remove the file patch2 after you finished. 07 Jul 16.
|
|
Alternatively, you can apply the patch listed above using the Unix patch command. Download the file patch2 anywhere on your computer, then cd to the Cloudy tsuite/auto directory and issue the command *patch < /path/to/patch2*. You can remove the file patch2 after you finished. 07 Jul 16.
|
|
|
|
|
|
-----
|
|
-----
|
|
|
|
|
... | @@ -198,7 +198,7 @@ These have been included in the C07.02.01 service release. |
... | @@ -198,7 +198,7 @@ These have been included in the C07.02.01 service release. |
|
|
|
|
|
-----
|
|
-----
|
|
|
|
|
|
The *_incident continua at 1215 and 4860 Angstroms were zero in the emergent line intensities*_. These appear in the emission-line print out with the labels "Inci" and the two wavelengths and can be used to print the line spectrum as equivalent widths rather than intensities (see the *observed quantities* section of Hazy 3). To fix, edit file prt_lines_continuum.cpp and add the following after line 227
|
|
The *incident continua at 1215 and 4860 Angstroms were zero in the emergent line intensities*. These appear in the emission-line print out with the labels "Inci" and the two wavelengths and can be used to print the line spectrum as equivalent widths rather than intensities (see the *observed quantities* section of Hazy 3). To fix, edit file prt_lines_continuum.cpp and add the following after line 227
|
|
|
|
|
|
```
|
|
```
|
|
if( LineSave.ipass > 0 )
|
|
if( LineSave.ipass > 0 )
|
... | @@ -208,7 +208,7 @@ The *_incident continua at 1215 and 4860 Angstroms were zero in the emergent lin |
... | @@ -208,7 +208,7 @@ The *_incident continua at 1215 and 4860 Angstroms were zero in the emergent lin |
|
|
|
|
|
```
|
|
```
|
|
|
|
|
|
Add the same code after the call to linadd that occurs four lines below this. After the change the code starting near line 227 will read as
|
|
Add the same code after the call to linadd that occurs four lines below this. After the change, the code starting near line 227 will read as
|
|
|
|
|
|
```
|
|
```
|
|
/* incident continuum nu*f_nu at H-beta, at illuminated face of cloud */
|
|
/* incident continuum nu*f_nu at H-beta, at illuminated face of cloud */
|
... | @@ -266,7 +266,7 @@ Photoexcitation of upper levels of split ground terms by the UV radiation field |
... | @@ -266,7 +266,7 @@ Photoexcitation of upper levels of split ground terms by the UV radiation field |
|
|
|
|
|
-----
|
|
-----
|
|
|
|
|
|
The *_set atomic data*_ command now has the option *_sulphur DR*_ to change the treatment of S dielectronic recombination. This change was merged into the C07.02.01 release. The guesses which are used when no DR data are available are now the mean of the logs of the DR rates. This is better due to the large dispersion in rate coefficients. Accurate DR rates do not now exist for low stages of ionization of S at photoionization temperatures. The relative [S III] / [S II] ratio is an important diagnostic indicator of conditions in many nebulae. This ratio depends on the DR rates chosen. This command changes the DR rates assumed for the lowest four ionization stages of S. The default, which can also be set with the keyword *__mix*_, is to use the larger of the Badnell (1991; ApJ, 379, 356 ) or guessed rates. The keyword *_pure*_ says to use only the Badnell rates. The keyword *_scale*_ says to use scaled oxygen DR rates. In this case one to four scale factors, one for each ionization stage, will be parsed off the command line. If fewer than four numbers occur then the last number entered will be used for the missing scale factors. The DR rate for ions of S will be equal to the DR rate for the same ionization stage of O multiplied by its scale factor.
|
|
The *set atomic data* command now has the option *_sulphur DR*_ to change the treatment of S dielectronic recombination. This change was merged into the C07.02.01 release. The guesses which are used when no DR data are available are now the mean of the logs of the DR rates. This is better due to the large dispersion in rate coefficients. Accurate DR rates do not now exist for low stages of ionization of S at photoionization temperatures. The relative [S III] / [S II] ratio is an important diagnostic indicator of conditions in many nebulae. This ratio depends on the DR rates chosen. This command changes the DR rates assumed for the lowest four ionization stages of S. The default, which can also be set with the keyword *__mix*_, is to use the larger of the Badnell (1991; ApJ, 379, 356 ) or guessed rates. The keyword *_pure*_ says to use only the Badnell rates. The keyword *_scale*_ says to use scaled oxygen DR rates. In this case one to four scale factors, one for each ionization stage, will be parsed off the command line. If fewer than four numbers occur then the last number entered will be used for the missing scale factors. The DR rate for ions of S will be equal to the DR rate for the same ionization stage of O multiplied by its scale factor.
|
|
|
|
|
|
-----
|
|
-----
|
|
|
|
|
... | @@ -278,15 +278,15 @@ The low-l *proton impact excitations* in the helium isoelectronic sequence were |
... | @@ -278,15 +278,15 @@ The low-l *proton impact excitations* in the helium isoelectronic sequence were |
|
|
|
|
|
-----
|
|
-----
|
|
|
|
|
|
The *print coolants command printed a corrupted string* due to a string overwrite. As a result some of the line labels were written together. The 07.02.01 bugfix rollup will contain a fix to this. 07 April 20. Thanks to Valentina Luridana for finding this problem.
|
|
The *print coolants command printed a corrupted string* due to a string overwrite. As a result, some of the line labels were written together. The 07.02.01 bugfix rollup will contain a fix to this. 07 April 20. Thanks to Valentina Luridana for finding this problem.
|
|
|
|
|
|
------
|
|
------
|
|
|
|
|
|
The *table command does not remove the filename that occurs in the table line, table read, and table star commands*, before parsing the command. This means that the filename can fool the parser. The 07.02.01 bugfix rollup will contain a fix to this. 07 April 20. Thanks for Susmita Chakravorty for finding this problem.
|
|
The *table command does not remove the filename that occurs in the table line, table read, and table star commands*, before parsing the command. This means that the filename can fool the parser. The 07.02.01 bugfix rollup will contain a fix to this. 07 April 20. Thanks to Susmita Chakravorty for finding this problem.
|
|
|
|
|
|
-----
|
|
-----
|
|
|
|
|
|
[ftp://gradj.pa.uky.edu/gary/cloudy_gold/hotfixes/patch1 patch1 (Unix patch)]
|
|
[Unix patch](http://data.nublado.org/cloudy_releases/c07_02/hotfixes/)
|
|
|
|
|
|
There is a bug that causes *the values for <Tden>, <dens>, <MolWgt>, Mean Jeans l(cm), and M(sun) to be wrong* in the Cloudy output. To fix the problem, two files need to be altered. First, edit the file zero.cpp on lines 1326 through 1328 as follows:
|
|
There is a bug that causes *the values for <Tden>, <dens>, <MolWgt>, Mean Jeans l(cm), and M(sun) to be wrong* in the Cloudy output. To fix the problem, two files need to be altered. First, edit the file zero.cpp on lines 1326 through 1328 as follows:
|
|
|
|
|
... | @@ -304,14 +304,12 @@ Second, edit the file iter_startend.cpp on lines 366 through 368 as follows: |
... | @@ -304,14 +304,12 @@ Second, edit the file iter_startend.cpp on lines 366 through 368 as follows: |
|
368 : colden.wmas = 0.;
|
|
368 : colden.wmas = 0.;
|
|
```
|
|
```
|
|
|
|
|
|
Alternatively you can apply the patch listed above using the Unix patch command. Download the file patch1 anywhere on your computer, then cd to the Cloudy source directory and issue the command *patch < /path/to/patch1*. You can remove the file patch1 after you finished. 07 Mar 26.
|
|
Alternatively, you can apply the patch listed above using the Unix patch command. Download the file patch1 anywhere on your computer, then cd to the Cloudy source directory and issue the command *patch < /path/to/patch1*. You can remove the file patch1 after you finished. 07 Mar 26.
|
|
|
|
|
|
------
|
|
------
|
|
|
|
|
|
Return to HotFixes main page
|
|
Return to [HotFixes](HotFixes) main page
|
|
|
|
|
|
Return to the StepByStep instructions
|
|
Return to the [StepByStep](StepByStep) instructions or go [home](home)
|
|
|
|
|
|
Return to main [WikiStart wiki] page
|
|
|
|
|
|
|
|
----- |
|
----- |