Hello Ben,
Thanks for the very thorough comments. Scripts, although useful, usually
don't get as much debugging as regular CIAO tools, so we really appreciate
outside help.
The first bug you mentioned, regarding tstart being an integer, was found not
too long ago. The latest version of that script, available on the CIAO web
page, includes a similar fix to what you mentioned. If you downloaded your
version of psextract prior to (roughly) Dec. 28th, then it's an older version.
I've seen the second bug, regarding the arf file having 'RSPFILE' misset, in
my own work. The header RSPFILE is equal to '0.1:11.0:0.01', just as in your
data. In my case, I used Sherpa to work with the spectrum. After loading the
data 'data source.pi', Sherpa automatically looks for associated files with the
same base, 'source.rmf' and 'source.arf'. Although Sherpa give an error
message similar to XSPEC (since it can't fine '0.1:11.0:0.01') it loads the
'source.rmf' file, and seems to use it properly.
I don't know the source of these numbers, but I'll be sure the psextract
developer gets this. Hopefully, we'll have another fix soon.
cheers,
casey
> Hello,
>
> I have downloaded the psextract script, and am now using it fairly
> successfully, but I have encountered the following problem...
> When the script uses the acis_fef_lookup script it passes it the values
> for chipx and chipy coordinates, and tstart, the start time, which it
> gets from dmstat. However the values it tries to pass are real numbers,
> while the input parameters of acis_fef_lookup are integers. This problem
> is simply solved by adding the lines
>
> #ALTERATION BEGINS# Convert chipx, chipy & tstart to integers (rounded):
> chipx=`echo $chipx | awk '{printf("%12i\n", $1) }'`
> chipy=`echo $chipy | awk '{printf("%12i\n", $1) }'`
> tstart=`echo $tstart | awk '{printf("%15i\n", $1) }'`
> #ALTERATION ENDS#
>
> before acis_fef_lookup is called (around line 250).
> The other minor problem that I'm having is that when I load the resultant
> spectra into XSPEC i get a warning that says...
>
> Warning : response file in ARF is not the same as that set
>
> and sure enough, the keyword RESPFILE in the newly generated $root.arf
> file is something like '0.1:11.0:0.01' I've tried changing this manually
> to $root.rmf using dmhedit, but this causes all manner of things to go
> wrong. Does anyone know what the '0.1:11.0:0.01' value means?
>
> Cheers,
> Ben
>
This archive was generated by hypermail 2b29 : Thu Dec 13 2012 - 01:00:04 EST