Re: problem using model_spectrum and brightest

    juan> It didn't work. I give you more details:

    juan> I define a model:

    juan> # id   Temp	Density    Abund    Norm    Vturb   
    juan> redshift
    juan> #      (K)	(cm^-3) 		    (km/s)
    juan> 1    3.e6	1.e-3	   1.0      0.0008635055     10.0   
    juan> 0.0
    juan> #
    juan> # abundances for component 1:
    juan> #     Si = 0.8	Na = 0.9   Fe = 0.3
    juan> #
    juan> 2    20.e6	1.e-3	   1.0      0.001866956    10.0   
    juan> 0.0



    juan> then I loaded a dataset, and evaluate the model as you
    juan> suggested:

Hi Juan,

That method doesn't work for me either - I'd report it to John Houck
(John?).  There are several other ways to define models which came
after the examples in the manual.

Here's how I define models:

isis> plasma(aped);
...
isis> p = default_plasma_state;
isis> p.temperature = 10^[6.2, 7.2] ; 
isis> p.norm = [ 0.0086, 0.0018 ] ; 
isis> p.elem = [Si, Na, Fe ] ;         %N.B.: no Na in APED.
isis> p.elem_abund = [0.8, 0.9, 0.3];

isis> create_aped_fun( "my_model", p ) ; 
isis> fit_fun( "my_model(1)" ) ; 

isis> list_par;
my_model(1)
 idx  param                 tie-to  freeze         value         min         max
  1  my_model(1).norm1          0     1           0.0086           0           0  
  2  my_model(1).norm2          0     1           0.0018           0           0  
  3  my_model(1).temperature1   0     1          1584893           0           0  
  4  my_model(1).temperature2   0     1     1.584893e+07           0           0  
  5  my_model(1).density        0     1                1           0           0  
  6  my_model(1).vturb          0     1                0           0           0  
  7  my_model(1).redshift       0     1                0           0           0  
  8  my_model(1).metal_abund    0     1                1           0           0  
  9  my_model(1).Si             0     1              0.8           0           0  
 10  my_model(1).Na             0     1              0.9           0           0  
 11  my_model(1).Fe             0     1              0.3           0           0  

isis> y = eval_fun( 1.0, 25 ) ; 
isis> page_group( brightest(5, where( wl( 12.0, 17.5 ) ) ) );
#  index        ion   lambda    F (ph/cm^2/s)  A(s^-1)  upper lower   label
   4137 *      Ne X    12.132    1.516e-05   6.164e+12     4     1 2p~^2P_{3/2} - 1s~^2S_{1/2}
   3948 *     Ne IX    13.447    1.694e-05   8.867e+12     7     1 1s2p~^1P_{1} - 1s^2~^1S_{0}
   3944 *     Ne IX    13.699    1.140e-05   1.087e+04     2     1 1s2s~^3S_{1} - 1s^2~^1S_{0}
   2375 *    O VIII    16.006    1.930e-05   6.739e+11     7     1 3p~^2P_{3/2} - 1s~^2S_{1/2}
   2199 *     O VII    17.396    1.924e-05   1.963e+11    37     1 1s5p~^1P_{1} - 1s^2~^1S_{0}


This way is good it you want several temperature components with a
common set of abundances and common vturb and redshift.

If you wanted all those per component, then define my_model with only
one component, and do...   

fit_fun( "my_model(1) + my_model(2)" );

You can, of course, package the model definition into a function or
script to define some commonly used cases.

(Don't try to name the model "aped", since that name is taken for the
database definition.)

-- Dave

----
You received this message because you are
subscribed to the isis-users list.
To unsubscribe, send a message to
isis-users-request_at_email.domain.hiddenwith the first line of the message as:
unsubscribe