|
|
|
|
|
# Notes on the 2016 meeting at Mexico
|
|
|
|
|
|
|
|
|
## Time and Place
|
|
|
|
|
|
Saturday 2016 Aug 6. We will have two full days of discussion, Aug 6 & 7.
|
|
|
|
|
|
------
|
|
|
|
|
|
|
|
|
## Some questions to discuss
|
|
|
|
|
|
* Cloudy review paper for C16 release
|
|
|
* Discussion of open RT problems
|
|
|
* the emergent spectrum in a closed geometry, is it fully solved?
|
|
|
* the discrepancies between line fluxes in the saved continuum and the line stack.
|
|
|
* can we improve on using exp(-tau) for diffuse radiation; Peter's proposal.
|
|
|
* a better description of the RT in Cloudy, this is largely lacking now.
|
|
|
* Discuss the new parser syntax.
|
|
|
* Should we move to C++11 after we branch C16?
|
|
|
* Maintaining an active user group on the web. Do we still want this?
|
|
|
* Switch to a newer chemistry. UDfA RATE12? KIDA??
|
|
|
* Computers in University of Kentucky.
|
|
|
|
|
|
------
|
|
|
|
|
|
|
|
|
## Saturday Aug 6 2016
|
|
|
|
|
|
|
|
|
|
|
|
18:00 adjourn for day
|
|
|
|
|
|
|
|
|
## Conclusions Saturday
|
|
|
|
|
|
* Review paper C16
|
|
|
* It will describe the physics that can be covered with Cloudy databases models (Stout, Chianti, iso-sequences).
|
|
|
* New Cloudy developments will be described in future short papers.
|
|
|
* Cloudy users will be asked to cite the paper corresponding to the version used.
|
|
|
* Publishing in an open access journal preferred.
|
|
|
* Rev. Mex. A. A. pros: continuity, journal longevity, open access; cons: no DOI, two volumes per year.
|
|
|
* Computers in University of Kentucky
|
|
|
* New 'cloud9' to be installed
|
|
|
* Old 'cloud9' to become 'nephos', 'nephos' to become radegund and be runned in 32b
|
|
|
* Do we need a 32b testing computer? To be thought about that in the future.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Sunday Aug 7 2016
|
|
|
|
|
|
|
|
|
|
|
|
18:00 adjourn for day
|
|
|
|
|
|
|
|
|
## Conclusions Sunday
|
|
|
|
|
|
* Should we move to C++11 after we branch C16?
|
|
|
* New features. Easier to program (e.g 'auto' ). Programmer friendlier.
|
|
|
* Concerns: Used with old compiler versions
|
|
|
* Agreed for the change.
|
|
|
* Switch to a newer chemistry. UDfA RATE12? KIDA??
|
|
|
* Currently, we are missing important species.
|
|
|
* UDfa seems to be a reasonable standard for astrophysics. Changing to another might introduce different 'problematic reactions'.
|
|
|
* RATE12 is not yet ready, but it is being checked. It would be the preference for future releases.
|
|
|
* RATE12 has many more reactions.
|
|
|
* RATE12 does not have static solutions in some regimes.
|
|
|
* Maintaining an active user group on the web. Do we still want this?
|
|
|
* Most question are answered.
|
|
|
* Yahoo group is already set up.
|
|
|
* Links in Hazy points to the group (Yahoo).
|
|
|
* We can choose where to point the links on the next release depending on the evolution of Yahoo policies.
|
|
|
* Discuss the new parser syntax.
|
|
|
* Some confusion with 'linear' or 'log' keywords.
|
|
|
* Users value the current syntax as very user friendly and supportive.
|
|
|
* Do something to get rid of the 'logs' in future releases depending on human resources.
|
|
|
* Different keywords read data files at different positions somewhat randomly, needs for rationalization. It may be difficult to find time resources to fix that.
|
|
|
* User data files should be in local directories.
|
|
|
* Rule for how to search for input data files. Search path: local directory:data directory. Rules should be the same in both directories.
|
|
|
* To be applied after C16 branch.
|
|
|
|
|
|
|
|
|
------
|
|
|
|
|
|
Return to DeveloperPages
|
|
|
|
|
|
Return to main [WikiStart wiki] page
|
|
|
|
|
|
------ |