Re: Comments.

Bulent KIZILTAN <bulent_at_email.domain.hidden>I've found out that if the .fits data header is not "standart", the pileup
>kernel picks up a set frame time instead of crashing or stopping the
>calcultaion. It also picks up the exposure time that is in the arf header

   (You do not really mean "crashing", since only really buggy software
   crashes.  Let's hope that isis does not fall into that class.)

>if the data header is not "standart". If not being careful, this might
>lead to inconsistent results.

The value that is hard coded into the pileup kernel is approriate for
the standard ACIS timed exposure mode.  Perhaps the next version will
have a mechanism for setting the frame time.

>It would be nice if those values could be set manually (I couldn't figure
>out a way to do this. I'd appreciate if anybody could tell me how to fix
>these values from the isis command line). It would also

It's been our experience with Chandra data products that the ARF
generally has the correct exposure time.  (This may nolonger be an
issue with recent versions of dmextract).  I think that for this reason,
isis chooses the arf's notion of EXPOSURE over that in the PHA file.
You can always change the arf's exposure value using the
set_arf_exposure function.  For example, to set the arf's exposure to
that of the PHA file, use, e.g.,

    isis> set_arf_exposure (1, get_hist_exposure (1));

>be nice to run isis without closing the edit_par window.

I do not see how this would be possible.  Isis spawns the editor to
edit the file and then waits for it to exit before continuing.  You
can always run the editor in a separate window and use load_par
instead of edit_par.

--John

----
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