8000 Tags · lime-rt/lime · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Tags: lime-rt/lime

Tags

v1.9.5

Toggle v1.9.5's commit message
Updated VERSION to 1.9.5

v1.9.4

Toggle v1.9.4's commit message
Attempts (but fails) to completely fix issue 271.

- The grid file is now written with DENSMOLn columns. As for reading of the grid file, if DENSMOLn columns are present, they will be read; if not, and if ABUNMOLn columns are present, they will be read. The existence of DENSMOLn columns is passed back to grid.c:readGridWrapper(), where it is used to set par->useAbun if appropriate, but in fact this has no wider effect on the task, since all the relevant initialization is already done by the time the grid file is read. This won't be fixable without some reorganization.

v1.9.3

Toggle v1.9.3's commit message
Incremented patch number.

v1.9.2

Toggle v1.9.2's commit message
Fixes #262

Two changes have been made.
  - In run.c:parseInput(), a warning is generated if (!par->lte_only && par->nSolveIters<=par->nSolveItersDone && !allBitsSet(par->dataFlags, DS_mask_populations)). I.e. if the user has neither set pops values via a submitted grid file, nor requested any solver iterations.
  - In run.c:run(), gp[gi].mol[si].pops is malloc'd and filled with zeros whether par->doSolveRTE is set or not.

Upshot of the changes are that, where previous the code would seg fault if the user left par->nSolveIters at default, now it will proceed, with a warning message. Any output images will contain zero contribution from line emission.

An additional change: in run.c:run(), formerly the decision to set par->doSolveRTE depended on (par->nSolveIters>0 || par->lte_only), now it depends on (par->nSolveIters>par->nSolveItersDone || par->lte_only).

v1.9.1

Toggle v1.9.1's commit message
Fixes #256.

v1.9

Toggle v1.9's commit message
A few minor changes:

  - In writefits.c, CRVAL for the Stokes axis has now (the correct value of) 1 rather than 0.

  - In writefits.c, CDELT values are written as floats rather than doubles. This is to stop the CASA viewer complaining.

  - In task_limesolver.py and task_raytrace.py, moldatfile is now expected to be a scalar not a list.

  - In task_limesolver.py, the user now has the choice to specify scalar values if they want to (instead of single-element lists) for functions ('scalarConst' or 'vectorConstR') which take only one parameter.

v1.8.2

Toggle v1.8.2's commit message
Updated version number.

v1.8.1

Toggle v1.8.1's commit message
Fixes for #243 and #244.

v1.8

Toggle v1.8's commit message
Several minor fixes.

v1.7.3

Toggle v1.7.3's commit message
Fix to #227

Changes as follows:
  - Added a message to aux.c.parseInput() when a moldat file is not found in the local directory and is sought in the LAMDA database instead.

  - Added a sanity check of the first line of the moldat file in tcpsocket.c.openSocket(). This is to trap the situation in which the user has requested a file which is available neither locally nor in LAMDA. What happens in this situation is that a file is created, but it just contains html reporting '404 - file not found'. There may be a more graceful way to trap such cases.

  - Added a similar check for local moldat files to aux.c.parseInput().

  - Added a call to readDummyCollPart() in molinit.c.readMolData() to keep file reading in sync in the case where !(par->collPartIds==NULL || cpFound) (thanks T Lunttila).
0