Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
planets_rt [2012/01/11 19:49] – [11 Jan 2012] mate | planets_rt [2012/02/28 20:12] (current) – [28 Feb 2012] mate | ||
---|---|---|---|
Line 4: | Line 4: | ||
* Make generalized RT code | * Make generalized RT code | ||
* Write code to make standard parameter files | * Write code to make standard parameter files | ||
+ | |||
+ | ===== 28 Feb 2012 ===== | ||
+ | We have a serious list of tasks ahead of us: | ||
+ | |||
+ | **atmosphere.pro: | ||
+ | - test for jupiter (I have written a runfile and a needed function for this already) | ||
+ | - get running for uranus and test | ||
+ | - get running for titan and test | ||
+ | **tau_gas.pro: | ||
+ | - test katherine' | ||
+ | - update makeparfile take any combination of input param files as strings? This would allow use of new param files, and multiple wavelength ranges to be specified. It would make code more transparent to outside user. | ||
+ | - incorporate all needed functions/ | ||
+ | - NH3 absorption: need to figure out why we'd want to use band models to get k coefficients. Is there a difference between the band model answer and the sromovsky answer? Why? Code in best choice. | ||
+ | - make tau_gas work with structure input and output | ||
+ | |||
+ | **tau_haze.pro** | ||
+ | - make into a structure | ||
+ | - allow for particle size distribution for calculating mie scattering | ||
+ | - Lots of questions to answer: how do we specify things? Where are the calculations done? Do we want to fit for g,w, and asym and back out particle properties, or the other way around? | ||
+ | |||
+ | **spectrum fitting:** | ||
+ | - test time to complete one run | ||
+ | - estimate number of parameters that need to be varied, total time to make a ' | ||
+ | - Mike's genetic algorithm | ||
+ | |||
+ | **Repository cleanup** | ||
+ | |||
+ | Update repository to ignore (large) reference data files: | ||
+ | - location of files can remain the same, however might need to re-initialize repository so that large files aren't downloaded as part of early changesets. | ||
+ | - Ignore DS_Store files. These things are regularly updated and don't need to be tracked. Everyone should create/edit the .hgignore_global file to exclude these files. | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | **other** | ||
+ | - Directory specification: | ||
===== 11 Jan 2012 ===== | ===== 11 Jan 2012 ===== | ||
Line 21: | Line 57: | ||
How to generalize composition? | How to generalize composition? | ||
- | A structure for compositions as nested structure. | + | A structure for compositions as nested structure |
+ | |||