From 8ef68669dd4153ebc2d827c6643f55554ed9b109 Mon Sep 17 00:00:00 2001 From: ichoubani Date: Tue, 15 Nov 2022 15:11:19 +0100 Subject: [PATCH] Accounting for all luminosity classes in test in stellar_population plugin --- src/idl/dustem_plugin_stellar_population.pro | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/src/idl/dustem_plugin_stellar_population.pro b/src/idl/dustem_plugin_stellar_population.pro index 7dbb273..95f4804 100644 --- a/src/idl/dustem_plugin_stellar_population.pro +++ b/src/idl/dustem_plugin_stellar_population.pro @@ -92,10 +92,14 @@ IF keyword_set(key) THEN BEGIN ;JPB: This is highly non standard and makes Fawlty go "Segmentation fault" ;lumclass = (strmid(key,2)).remove(-1) ; extracting the luminosity class strings + ;IC: Yes but we need to take into account when luminosity class is two characters and not just one. ie: IV instead of V. + ;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. lumclass=strarr(n_elements(key)) FOR i=0L,n_elements(key)-1 DO BEGIN - lumclass[i]=strmid(key[i],2,1) + lumclass[i]=strmid(key[i],2,strlen(key[i])-3) ENDFOR + + params = strmid(key,0,/reverse_offset) ; extracting the indices (in the 'key' array) of the stellar parameters to fit ; Locating the O3 stellar population parameters - this new code structure accounts for the presence of different luminosity classes. -- libgit2 0.21.2