Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
planets_rt [2012/01/05 22:22] – [05 Jan 2011] mateplanets_rt [2012/02/28 20:12] (current) – [28 Feb 2012] mate
Line 5: Line 5:
     * Write code to make standard parameter files     * Write code to make standard parameter files
  
-===== 05 Jan 2011 =====+===== 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's new code for ch4 coefficients 
 +      - 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/files into one program (e.g. all rayleigh scattering, nh3 absorption, h2h2, etc coefficients covering relevent T and frequency) 
 +      - 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 'cube' of models to compare each spectrum to  
 +      - 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: This is complicated during development, because, e.g. Statia's input TP profiles are within the 'neptune' refdata directory, while other files are (or should be) common. Some things (e.g. Katherine's stuff) are not even in the repository for various reasons. It would be best not have to specify full paths for things, and have the program automatically look for ref files and procedures in the right place.  
 + 
 +===== 11 Jan 2012 ===== 
 + 
 +**Notes:** 
 + 
 +Statia describes the atmosphere stucture: 
 + 
 +Temperature and pressure profiles from either ASCII file or procedure to generate T/P profile.  
 + 
 +Mike: Units - mixing ratio relative to H2 (not mole fraction) should be documented in input structure. Works for giant planets but might be a problem for Titan.  
 + 
 +Having a text file or procedure as input can decrease the learning curve and allows for text file manipulation. 
 + 
 +Error handling with 'STOP' or 'CRASH' a nice start. Is it sufficient? 
 + 
 +How to generalize composition? Various numbers and types of species in solar system targets, and perhaps motivated by exoplanets? 
 + 
 +A structure for compositions as nested structure within atmosphere. 
 + 
 + 
 + 
 + 
 +===== 05 Jan 2012 =====
  
 **Notes:** **Notes:**
Line 32: Line 89:
  * 11am Wednesday, 11 Jan 2012. (B40)  * 11am Wednesday, 11 Jan 2012. (B40)
  
-**Note on sourcing path:**+**Note on sourcing the environment configuration file:**
  
 Mate made a mistake on trying to use: ''~$ source config'' to set/edit the environment parameters from the command line... it turns out that ''config'' is an OpenSSL library configuration utility, hence the error. Renaming the configuration file to: ''configenv'' makes everything work out swell. An example is below: Mate made a mistake on trying to use: ''~$ source config'' to set/edit the environment parameters from the command line... it turns out that ''config'' is an OpenSSL library configuration utility, hence the error. Renaming the configuration file to: ''configenv'' makes everything work out swell. An example is below:
  
-''---------------------------------------------------------------------------------------------- 14:07:04 
  
 +<code>
 +---------------------------------------------------------------------------------------------- 14:07:04
 mate@gina:~$ echo $RT_PATH mate@gina:~$ echo $RT_PATH
- 
  
 ---------------------------------------------------------------------------------------------- 14:07:14 ---------------------------------------------------------------------------------------------- 14:07:14
- 
 mate@gina:~$ pwd mate@gina:~$ pwd
- 
 /Users/mate /Users/mate
- 
 ---------------------------------------------------------------------------------------------- 14:07:19 ---------------------------------------------------------------------------------------------- 14:07:19
- 
 mate@gina:~$ source ~/planets/rt/configenv  mate@gina:~$ source ~/planets/rt/configenv 
- 
 ---------------------------------------------------------------------------------------------- 14:07:32 ---------------------------------------------------------------------------------------------- 14:07:32
- 
 mate@gina:~$ echo $RT_PATH mate@gina:~$ echo $RT_PATH
- 
 /Users/mate/planets/rt /Users/mate/planets/rt
- 
 ---------------------------------------------------------------------------------------------- 14:07:35 ---------------------------------------------------------------------------------------------- 14:07:35
- 
 mate@gina:~$ source ~/someotherdir/configenv  mate@gina:~$ source ~/someotherdir/configenv 
- 
 ---------------------------------------------------------------------------------------------- 14:07:56 ---------------------------------------------------------------------------------------------- 14:07:56
- 
 mate@gina:~$ echo $RT_PATH mate@gina:~$ echo $RT_PATH
- 
 /Users/mate/someotherdir /Users/mate/someotherdir
 ---------------------------------------------------------------------------------------------- 14:07:58 ---------------------------------------------------------------------------------------------- 14:07:58
- 
 mate@gina:~$ echo $IDL_PATH mate@gina:~$ echo $IDL_PATH
- 
 +/Users/mate/someotherdir/titan/pro:+/Users/mate/someotherdir/xxx/pro:+/Users/mate/someotherdir/refdata/pro:+/Users/mate/planets/rt/titan/pro:+/Users/mate/planets/rt/xxx/pro:+/Users/mate/planets/rt/refdata/pro:+/Applications/itt/idl/lib:+/Users/mate/idl/:/Users/mate/disk/chem/src.pro:+/Users/mate/disk/xray +/Users/mate/someotherdir/titan/pro:+/Users/mate/someotherdir/xxx/pro:+/Users/mate/someotherdir/refdata/pro:+/Users/mate/planets/rt/titan/pro:+/Users/mate/planets/rt/xxx/pro:+/Users/mate/planets/rt/refdata/pro:+/Applications/itt/idl/lib:+/Users/mate/idl/:/Users/mate/disk/chem/src.pro:+/Users/mate/disk/xray
 +</code>
  
----------------------------------------------------------------------------------------------- 14:08:10 +At first there is no environment variable for ''RT_PATH''. Then sourcing the enviroment configuration file sets the directory. Sourcing the configuration from a different directory (a hypothetical repository) resets the variable. In this example neither file is sourced from within the repository.
-'' +
- +
- +
- +
  
 +The IDL_PATH is appended with the most recent configuration at the top of the path (where IDL looks first). This path information is reset when opening a new shell. 
  
  

Trace: