On Mon, 2006-06-05 at 15:28 -0400, Antonella Fruscione wrote:
> ---------------------------------------------------------------
>
> Providing your name is optional.
>
> First Name:
> Last Name:
>
> 1. Do you use Sherpa for modeling and fitting your data?
> Always Never Occasionally (what percentage?)
>
Always
> 2. If "never" or "occasionally", what modeling and fitting package are
> you using? (xspec, isis, idl, pintofale)
> Other (which?)
>
> 3. What kind of data do you mostly work with?
> x-ray X Optical X Other (which?)
> spectral X spatial X data cubes timing
>
> 4. When you use Sherpa, do you mostly use it in interactive mode (see
> example 1), do you use scripts (see example 2) or a combination of the two?
> interactive mode scripts both
>
both
> 5. When you use it in interactive mode, are you using the command
> language (see example 1) or the S-Lang functions (see example 3)?
> Command language S-Lang functions
>
both/mixed
> 6. When you use Sherpa scripts, what percentage of the scripts are ?
> - pure Sherpa command language scripts (e.g. generated by a "save all"
> command at the end of a session) (see example 4)
> - pure S-Lang scripts (see example 5)
> - a mix of Sherpa, ChIPS, and/or S-Lang commands (see example 6)
>
80% mixed
> 7. Roughly how many Sherpa scripts do you have?
> a few (<10) : many (<50) : a lot (>50) :
>
many
> 8. We are investigating the possibility of in future adding a new Python
> language interface to Sherpa & ChIPS, if resources allow.
> Are you familiar with the Python language? Yes: No: X
> If yes, would you use Sherpa more often if it was available in Python?
> Yes: No:
>
> 9. Do you use scripts for the ChIPS plotting package?
> Yes: X No:
> If so, are they command language scripts, S-Lang scripts, or a mixture?
> Command language: S-Lang: Mixture: X
>
> 10. How important it is for you to keep the command language interface
> and S-Lang interface in Sherpa and ChIPS? (use a 1 to 10 scale)
> Command language : 1 (1=very, 5=somewhat, 10=not at all.)
> S-Lang : 1 (1=very, 5=somewhat, 10=not at all.)
>
> 11. How important for your analysis is backward compatibility of
> interfaces and scripting when compared to increased functionality or a
> more robust code? (use a 1 to 10 scale)
> (1=very, 5=somewhat, 10=not at all.)
>
1
> 12. Which is your primary computer platform (select one)?
> Solaris 10: MacOSX 10.4 MacOSX 10.3 Linux Fedora Core 3 X
> Other:
>
> 13. Do you have any plans to switch (e.g. solaris to linux, linux to
> mac, mac powerpc to intel) in the next couple of years?
> from where: to where: MAC
>
> 14. In your opinion how important it is to have a stand alone sherpa
> that can be downloaded independently from the CIAO software? (e.g. to
> make it easier to use with other analysis systems) (use a 1 to 10
> scale) (1=very, 5=somewhat, 10=not at all.)
>
5
> -----------------------------------------------------------------------
>
> Examples
>
> EXAMPLE 1: using Sherpa in interactive mode with the command language
>
> prompt% sherpa
> -----------------------------------------------------
> Welcome to Sherpa: CXC's Modeling and Fitting Program
> -----------------------------------------------------
> sherpa> DATA 3c273.pi
> sherpa> SHOW
> sherpa> NOTICE ENERGY 0.1:6.0
> sherpa> SUBTRACT
> sherpa> SOURCE = xsphabs[abs]*powlaw1d[p1]
> sherpa> FIT
> sherpa> SAVE ALL example.sherpascript
>
>
> EXAMPLE 2: running Sherpa via scripts
>
> prompt% sherpa myscript.sherpa
>
> OR
>
> prompt% sherpa
> -----------------------------------------------------
> Welcome to Sherpa: CXC's Modeling and Fitting Program
> -----------------------------------------------------
> sherpa> use myscript.sherpa
>
> OR
>
> prompt% slsh myscript.sl
>
>
> EXAMPLE 3: using Sherpa in interactive mode with S-Lang functions
>
> prompt% sherpa
> -----------------------------------------------------
> Welcome to Sherpa: CXC's Modeling and Fitting Program
> -----------------------------------------------------
> sherpa> load_dataset("3c273.pi")
> sherpa> () = set_notice(,0.1,6.0)
> sherpa> () = set_source_expr("xsphabs[abs]*powlaw1d[p1]")
> sherpa> () = set_subtract
> sherpa> good = run_fit
>
>
> EXAMPLE 4: a pure Sherpa command language script
>
> PARAMPROMPT OFF
> DATA 3c273.pi
> NOTICE ENERGY 0.1:6.0
> SUBTRACT
> SOURCE = xsphabs[abs]*powlaw1d[p1]
> FIT
>
>
> EXAMPLE 5: a pure S-Lang script
>
> () = load_dataset("3c273.pi");
> () = set_notice(,0.1,6.0);
> () = set_subtract();
> () = set_source_expr("xsphabs[abs]*powlaw1d[p1]");
> () = set_par("abs.nh","value",0.07);
> () = set_frozen("abs");
> variable good = run_fit();
> variable conf = run_cov();
>
>
> EXAMPLE 6: a "mixed" script
>
> PARAMPROMPT OFF
> DATA 3c273.pi
> NOTICE ENERGY 0.1:6.0
> SUBTRACT
> SOURCE = xsphabs[abs]*(xspowerlaw[p1]+xsgauss)
> FIT
> PROJECTION
> proj=get_proj
> eqwidth(xspowerlaw,xspowerlaw+xsgauss)
> ()=set_par("xsgauss.norm","value",proj[0].vhi)
> ew=get_eqwidth(1,"xspowerlaw","xspowerlaw+xsgauss")
> eew=ew*1000
> sprintf("UL Fe line EW = %4.0f eV ",eew)
>
>
This archive was generated by hypermail 2b29 : Thu Dec 13 2012 - 01:00:09 EST