Welcome to iraf.net Monday, May 29 2017 @ 11:26 AM GMT


 Forum Index > Archives > Sitemail Archives
 doecslit automation
   
Anonymous: Guest
 04/04/2002 09:36AM (Read 1093 times)  



Dear IRAF support group,I'm writing to you to ask for suggestions in the following item: I'm
writing an automatic reduction pipeline for the multi-echelle fiber
spectrograph GOHSS, for the TNG telescope, and I use the DOECSLIT task
(ECHELLE package) as the core tool for the spectra extraction.
All works ok, but I wish my procedure to be fully automatic, while
DOECSLIT always prompt me with yes/no questions each time it process a
new target from the target list:it asks for example: Edit apertures for no_bp_ds_out_flat_lamps_J+H_fib01? (yes): no Fit traced positions for no_bp_ds_out_flat_lamps_J+H_fib01
interactively? (yes): noand similar questions, and to all of them I have to manually reply "no".Is it possible to reply "no" in an automatic way e.g. from a text file
which contains all the replies?More, the DOECSLIT task calls the ECIDENTIFY task when it is required to
do the Waveleght calibration by using the arc lamps. The parameters for
ECIDENTIFY such as the xorder and yorder of the fit should be set via
the i_xorder and i_yorder of the SPARAMS parameters for example: sparams.i_xorder = 2.
sparams.i_yorder = 3.but it turns out that DOECSLIT does not consider them, always making the
fit with the default xorder=2 and yorder=1. The only way I found to
change them is the interactive colon commands: do I made a mistake?
Thank you very much for your attention and evaluable help.Gianluca Li Causi
--
______________________________________
Dr. Gianluca Li Causi
Osservatorio Astronomico di Roma
V. Frascati, 33
00040 Monteporzio (Roma)
Italy
tel.: +39 06 9428 6491
E-mail: licausi@coma.mporzio.astro.it
http://www.mporzio.astro.it/~licausi/

 
Anonymous: Guest
 04/04/2002 09:36AM  



Good Afternoon, The expert in this area is not available at this time, so I will attempt
to help you. I will also send my response to the expert so he may add
additional comments. While the 'doecslit' task is designed to accomplish many needed reduction
steps in an efficient manner, it does not appear that it was designed to
run *entirely* in a non-interactive fashion. As an aside (though this does
not address running the task in a non-interactive mode) if your response to
each initial version of a question is NO (upper-case is important), then you
will not be prompted for this particular question again. A "no" is
different than "NO"; the former is a response to a single question, the
latter will suppress the query for subsequent images. Perhaps I am misunderstanding, but you indicated you want your "pipeline"
to run in a fully automatic mode, but tasks like 'ecidentify' require
interaction from the user, so I am not sure what you mean by "automatic". As for the i_xorder and i_yorder parameters specified in 'sparams', I can
see that these values are being passed to the 'ecidentify' program in the
'doecslit' task. Please note the default values are i_xorder=3 and
i_yorder=3 in 'sparams' (not i_xorder=2 and i_yorder=1). I fear that I am not experienced enough with these tasks to address your
questions adequately. I will talk with the expert on Monday to see
if I can clarify your issues more thoroughly. Sorry for the delay.
Best,
Michele De La Peņa

 
Anonymous: Guest
 04/04/2002 09:36AM  



Michele De la Pena wrote:> Good Afternoon,
>
> The expert in this area is not available at this time, so I will attempt
> to help you. I will also send my response to the expert so he may add
> additional comments.
>
> While the 'doecslit' task is designed to accomplish many needed reduction
> steps in an efficient manner, it does not appear that it was designed to
> run *entirely* in a non-interactive fashion. As an aside (though this does
> not address running the task in a non-interactive mode) if your response to
> each initial version of a question is NO (upper-case is important), then you
> will not be prompted for this particular question again. A "no" is
> different than "NO"; the former is a response to a single question, the
> latter will suppress the query for subsequent images.Thank you very much for your reply, anyway, I would need to say "no" or "NO"
automatically at the first question, if possible, because I run the task on lots
of images for which I have different references.> Perhaps I am misunderstanding, but you indicated you want your "pipeline"
> to run in a fully automatic mode, but tasks like 'ecidentify' require
> interaction from the user, so I am not sure what you mean by "automatic".I create an ec*.ec file in the database, for each image with the initial guess
for the wavelenght solution (that I've done manually before), so that I could in
principle run ecidentify in a completely automathic way, the initial guess beeing
used to automatically identify spectral lines.
> As for the i_xorder and i_yorder parameters specified in 'sparams', I can
> see that these values are being passed to the 'ecidentify' program in the
> 'doecslit' task. Please note the default values are i_xorder=3 and
> i_yorder=3 in 'sparams' (not i_xorder=2 and i_yorder=1).
>
> I fear that I am not experienced enough with these tasks to address your
> questions adequately. I will talk with the expert on Monday to see
> if I can clarify your issues more thoroughly.
>Thank you very much for your next replies.Greetings
Gianluca Li Causi--
______________________________________
Dr. Gianluca Li Causi
Osservatorio Astronomico di Roma
V. Frascati, 33
00040 Monteporzio (Roma)
Italy
tel.: +39 06 9428 6491
E-mail: licausi@coma.mporzio.astro.it
http://www.mporzio.astro.it/~licausi/

 
Anonymous: Guest
 04/04/2002 09:36AM  



Good Morning, I just spent some time talking with the expert in this area regarding
your desire to create an automated pipeline using 'doecslit'. In essence, the way the 'doecslit' task is set up, you cannot avoid having
to answer a few queries. The reason is that 'doecslit' is a series of CL
scripts, where the settings for many of the query parameters have had their
values hardcoded in the scripts. However, there is a way to solve your
problem. A simple way to address your problem is to do the following (this is just
an example): 1) Copy the sproc.cl file from the doecslit$ source directory to a local
working directory ec> copy doecslit$sproc.cl . 2) Make sure the 'echelle' package is loaded; this is very important. 3) Redefine the 'sproc' task to your local version ec> redefine sproc=sproc.cl 4) Now you can edit "your" sproc.cl file to do what you wish. At the
least it looks like you will need to change to the lines of code below
to these new values: Line 121: apslitproc.ansedit = "NO"
Line 123: apslitproc.ansfittrace = "NO"
Line 155: apslitproc.anstrace = "YES" Be careful as some of the yes/no answers are responses as to whether
something will be done at all, and others are answers as to whether
the action should be done interactively. I caution that you may need to do some experimenting to achieve your
desired results. Perhaps the better answer to your question is for you to copy the entire
'doecslit' task (everything in the doecslit$ directory) to your own private
version. You can then modify any of the scripts to suit your needs. Since
these programs are all CL scripts, you will not have to compile any code.
If you choose this route, you will need to make sure you load the 'imred'
package, and then you will need to reset the definition of 'doecslit' to your
private version. You will see the following line in the "imred.cl" file
in the 'imred' source directory set doecslit = "imred$src/doecslit/" and you will need to reset 'doecslit' so your version is invoked.

Good Luck and I hope this better addresses your question,
Michele

 
Anonymous: Guest
 04/04/2002 09:36AM  



----- Begin Included Message ----->From licausi@coma.mporzio.astro.it Fri Apr 12 05:16 MST 2002
X-Autogenerated: Mirror
X-Mirrored-by: <delapena@noao.edu> (Michele De La Pena)
Date: Fri, 12 Apr 2002 14:18:34 +0200
From: Gianluca Li Causi <licausi@coma.mporzio.astro.it>
X-Accept-Language: en
MIME-Version: 1.0
To: Michele De la Pena <delapena@noao.edu>
Subject: Re: doecslit automation
Content-Transfer-Encoding: 7bitMichele De la Pena wrote:> Perhaps the better answer to your question is for you to copy the entire
> 'doecslit' task (everything in the doecslit$ directory) to your own private
> version. You can then modify any of the scripts to suit your needs. Since
> these programs are all CL scripts, you will not have to compile any code.
> If you choose this route, you will need to make sure you load the 'imred'
> package, and then you will need to reset the definition of 'doecslit' to your
> private version. You will see the following line in the "imred.cl" file
> in the 'imred' source directory
>
> set doecslit = "imred$src/doecslit/"
>
> and you will need to reset 'doecslit' so your version is invoked.
>
> Good Luck and I hope this better addresses your question,
> MicheleGREAT !!!!!
Yes, I've tried this route and it works just as I want!Thank you very much for this suggestion, it has been very useful for my work.Greetings
Gianluca
--
______________________________________
Dr. Gianluca Li Causi
Osservatorio Astronomico di Roma
V. Frascati, 33
00040 Monteporzio (Roma)
Italy
tel.: +39 06 9428 6491
E-mail: licausi@coma.mporzio.astro.it
http://www.mporzio.astro.it/~licausi/
----- End Included Message -----

 
   

Normal Topic Normal Topic
Sticky Topic Sticky Topic
Locked Topic Locked Topic
New Post New Post
Sticky Topic W/ New Post Sticky Topic W/ New Post
Locked Topic W/ New Post Locked Topic W/ New Post
View Anonymous Posts 
Anonymous users can post 
Filtered HTML Allowed 
Censored Content 
dog allergies remedies cialis 20 mg chilblain remedies


Privacy Policy
Terms of Use

User Functions

Login