Commit 8ef68669dd4153ebc2d827c6643f55554ed9b109
1 parent
75359080
Exists in
master
Accounting for all luminosity classes in test in stellar_population plugin
Showing
1 changed file
with
5 additions
and
1 deletions
Show diff stats
src/idl/dustem_plugin_stellar_population.pro
... | ... | @@ -92,10 +92,14 @@ IF keyword_set(key) THEN BEGIN |
92 | 92 | |
93 | 93 | ;JPB: This is highly non standard and makes Fawlty go "Segmentation fault" |
94 | 94 | ;lumclass = (strmid(key,2)).remove(-1) ; extracting the luminosity class strings |
95 | + ;IC: Yes but we need to take into account when luminosity class is two characters and not just one. ie: IV instead of V. | |
96 | + ;But since we only have MS (V) data, (lumclass[i]=strmid(key[i],2,1)) should be ok but I'm correcting it for future input. | |
95 | 97 | lumclass=strarr(n_elements(key)) |
96 | 98 | FOR i=0L,n_elements(key)-1 DO BEGIN |
97 | - lumclass[i]=strmid(key[i],2,1) | |
99 | + lumclass[i]=strmid(key[i],2,strlen(key[i])-3) | |
98 | 100 | ENDFOR |
101 | + | |
102 | + | |
99 | 103 | params = strmid(key,0,/reverse_offset) ; extracting the indices (in the 'key' array) of the stellar parameters to fit |
100 | 104 | |
101 | 105 | ; Locating the O3 stellar population parameters - this new code structure accounts for the presence of different luminosity classes. | ... | ... |