Up to top level
AO15   AO16   AO17   AO18   Backgrounds   Calibration   Conference   Data   Docs   EPICMOS   EPICpn   Feedback   Gallery   Misc   OM   Pending   PhD_Theses   Publications   RGS   RadMonitor   SAS_Hardware   SAS_WS   SASv16.0   SASv16.0_Installation   SASv16.1   SASv16.1_Installation   SASv17.0   SASv17.0_Installation   SASv18.0   SASv18.0_Installation   SciSim   Simulators_other   Suggestions   Trash   Visibility   XMM-bouncing   XMM-news   XRPS   XSA   esas   incoming  

Logged in as guest

Viewing esas/43949
Full headers

From: dbh@physast.uga.edu
Subject: mos_back
Compose reply
Download message
Move To:
4 replies: 1 2 3 4
2 followups: 1 2

Private message: yes  no

Notes:

Notification:


Date: Mon, 17 May 2010 22:47:25 GMT
From: dbh@physast.uga.edu
To: xmmhelp@sciops.esa.int
Cc: dbh@physast.uga.edu
Subject: mos_back
Full_Name: David Henley
Submission from: (NULL) (72.28.180.254)


SAS:     10.0.0 + latest patch
HEASOFT: 6.9
System:  Kubuntu 10.04, 2.6.32-22 Linux kernel (I've tried both a 64-bit machine
and a 32-bit virtual machine)


I am having problem running mos_back on obs. 0402560501 (the specific
observation isn't important to me - I'm just trying out the latest ESAS
software).

mos-filter and mos-spectra both seem to run fine. However, on a 32-bit virtual
Linux machine, mos_back segmentation faults. On a 64-bit Linux machine, mos_back
doesn't die, but the background spectrum is not created properly. The CHANNEL
and COUNTS columns in the SPECTRUM extension contain only 0s.

My mos_back invocation is as follows:

mos_back prefix=1S001 caldb=/home/dbh/astrosoft/xmm-esas/ccf diag=0 \
	elow=0 ehigh=0 ccd1=1 ccd2=1 ccd3=1 ccd4=0 ccd5=1 ccd6=0 ccd7=1

Below I've pasted the mos_back output from the two machines.

Regards,

Dave Henley

----------------------------------------------------------------------
- 32-bit virtual machine

 xmmdir: /home/dbh/astrosoft/xmm-esas/ccf
 diag:  0
 prefix: 1S001
 mosnum:  1
 obj_file: mos1S001-obj.pi
 obj_rmf: mos1S001.rmf
 el, eh:  0 0
 CCD selection 1 1 1 0 1 0 1
 WARNING: if chip 3, 4 or 6 are missing spurious
 gold features can arise in the 2.04-2.33,
 9.38-9.98, 11.03-11.82 keV regions
 Process the observation data
 Backscale and exposure from the observation data
 Chip  1  backscale=   1.6266296E+08  exposure =   5.0545410E+04
 Chip  2  backscale=   1.0901646E+08  exposure =   5.0584273E+04
 Chip  3  backscale=   6.0418408E+07  exposure =   5.0616422E+04
 Chip  5  backscale=   1.0673821E+08  exposure =   5.0562984E+04
 Chip  7  backscale=   1.1046149E+08  exposure =   5.0492250E+04
 Process the FWC data from the object region
 Backscale and exposure from the FWC data
 Chip  1  backscale=   1.6187579E+08  exposure =   1.0300928E+06
 Chip  2  backscale=   1.0778292E+08  exposure =   1.0444642E+06
 Chip  3  backscale=   6.0418408E+07  exposure =   1.0446921E+06
 Chip  5  backscale=   1.0673821E+08  exposure =   9.8330825E+05
 Chip  7  backscale=   1.1046149E+08  exposure =   1.0427332E+06
 Process the observation data from the corner regions
  /home/dbh/astrosoft/xmm-esas/ccf
 mosnam 1
 qpb_fi /mos1-1qpb.fits.gz
 /home/dbh/astrosoft/xmm-esas/ccf/mos1-2qpb.fits.gz
 Rate:    4.3293282E-02  Rate error:    1.6282988E-03
 Hard:    4.2363634  Hard error:    1.4516218
 Exposure:    1.0297362E+06
 Exposure weighted count rate:    3.8147632E-02
 Observation count rate:    4.3293282E-02  and correction scale factor:   
0.8811443
 2   3.0503132E+07   9.5793150E+05
  /home/dbh/astrosoft/xmm-esas/ccf/mos1-2qpb.fits.gz
 mosnam 1
 qpb_fi /mos1-2qpb.fits.gz
 /home/dbh/astrosoft/xmm-esas/ccf/mos1-3qpb.fits.gz
 Rate:    3.6766723E-02  Rate error:    1.4842317E-03
 Hard:    5.6290321  Hard error:    1.7459917
 Exposure:    1.0101831E+06
 Exposure weighted count rate:    3.0971613E-02
 Observation count rate:    3.6766723E-02  and correction scale factor:   
0.8423817
 3   2.8872112E+07   9.0157619E+05
  /home/dbh/astrosoft/xmm-esas/ccf/mos1-3qpb.fits.gz
 mosnam 1
 qpb_fi /mos1-3qpb.fits.gz
 /home/dbh/astrosoft/xmm-esas/ccf/mos1-5qpb.fits.gz
 Rate:    6.2852301E-02  Rate error:    1.9510473E-03
 Hard:    4.8130083  Hard error:    1.0802393
 Exposure:    1.0027021E+06
 Exposure weighted count rate:    5.2839223E-02
 Observation count rate:    6.2852301E-02  and correction scale factor:   
0.8406888
 5   4.8407928E+07   8.9352338E+05
  /home/dbh/astrosoft/xmm-esas/ccf/mos1-5qpb.fits.gz
 mosnam 1
 qpb_fi /mos1-5qpb.fits.gz
 /home/dbh/astrosoft/xmm-esas/ccf/mos1-7qpb.fits.gz
 Rate:    4.5511935E-02  Rate error:    1.6886560E-03
 Hard:    4.3714285  Hard error:    1.3795446
 Exposure:    1.0029362E+06
 Exposure weighted count rate:    3.9917793E-02
 Observation count rate:    4.5511935E-02  and correction scale factor:   
0.8770841
 7   3.3322676E+07   9.3015169E+05
 Backscale and augmented exposure from the corners of the observation data
 Chip  2  backscale=   3.0503132E+07  exposure =   9.5793150E+05
 Chip  3  backscale=   2.8872112E+07  exposure =   9.0157619E+05
 Chip  5  backscale=   4.8407928E+07  exposure =   8.9352338E+05
 Chip  7  backscale=   3.3322676E+07  exposure =   9.3015169E+05
 Process the observation data from the center chip
 N_SIMS:  3
 2 3 7
 Chip 1  observation corner total:    1.1116046E-09
 Chip 2  observation corner total:    1.1652679E-09
 Chip 3  observation corner total:    1.1032494E-09
 Chip 5  observation corner total:    1.1298465E-09
 Chip 7  observation corner total:    1.1297896E-09
 Process the FWC corner data
 Backscale and augmented expSegmentation fault



----------------------------------------------------------------------
- 64-bit machine

 xmmdir: /home/dbh/astrosoft/xmm-esas/ccf
 diag:  0
 prefix: 1S001
 mosnum:  1
 obj_file: mos1S001-obj.pi
 obj_rmf: mos1S001.rmf
 el, eh:  0 0
 CCD selection 1 1 1 0 1 0 1
 WARNING: if chip 3, 4 or 6 are missing spurious
 gold 

Message of length 9111 truncated

Reply 1

Resend
From: Pedro M. Rodriguez Pascual <xmmhelp@sciops.esa.int>
To: dbh@physast.uga.edu
Subject: Re: mos_back (PR#43949)
Date: Tue May 18 09:05:21 2010
Hello David,

We have forwarded your question to SAS developers for a detailed analysis. As
soon as we have a report , it will be sent back to you.

Sincerely,

Pedro



Reply 2

Resend
From: Pedro M. Rodriguez Pascual <xmmhelp@sciops.esa.int>
To: dbh@physast.uga.edu
Subject: Re: mos_back (PR#43949)
Date: Mon May 24 11:46:23 2010
David,

Unfortunately, the actual origin of the problem reported has not yet been fully
understood. It has been found that the initialization of some parameters in
calls to fitsio routines may lead to unexpected errors, but developers are not
completely sure that it is really the origin of the problem and, therefore, are
still analyzing the case.

We will come back when further news are available.

Sincerely,

Pedro


Followup 1

Compose reply
Download message
Date: Wed, 4 Aug 2010 16:15:10 -0400
Subject: Re: mos_back (PR#43949)
From: David Henley <dbh@physast.uga.edu>
To: "Pedro M. Rodriguez Pascual" <xmmhelp@sciops.esa.int>
Dear Pedro,

I've been working on other things recently, and have only just come
back to looking at this problem.

The patched version of ESAS seems to have solved the problem that I
originally reported. However, I'm now having similar problems to those
reported by Terry Gaetz (SASv10.0/43944), in that mos_back is
producing NaNs:

 xmmdir: /home/dbh/astrosoft/xmm-esas/ccf

 diag:  0
 prefix: 1S001
 mosnum:  1
 obj_file: mos1S001-obj.pi

 obj_rmf: mos1S001.rmf

 el, eh:  0 0
 CCD selection 1 1 1 0 1 0 1
 WARNING: if chip 3, 4 or 6 are missing spurious
 gold features can arise in the 2.04-2.33,
 9.38-9.98, 11.03-11.82 keV regions
 CalDB Directory: /home/dbh/astrosoft/xmm-esas/ccf

 mosnam 1
 qpb_fi /mos1-qpb.fits.gz
 CalDB QPB FIle: /home/dbh/astrosoft/xmm-esas/ccf/mos1-qpb.fits.gz

 Process the observation data
 Backscale and exposure from the observation data
 Chip  1  backscale=   1.6266296E+08  exposure =   5.0486500E+04
 Chip  2  backscale=   1.0901646E+08  exposure =   5.0525281E+04
 Chip  3  backscale=   6.0418408E+07  exposure =   5.0557254E+04
 Chip  5  backscale=   1.0673821E+08  exposure =   5.0503758E+04
 Chip  7  backscale=   1.1046149E+08  exposure =   5.0433355E+04
 Process the FWC data from the object region
 Backscale and exposure from the FWC data
 Chip  1  backscale=   1.6187579E+08  exposure =   1.0300928E+06
 Chip  2  backscale=   1.0778292E+08  exposure =   1.0444642E+06
 Chip  3  backscale=   6.0418408E+07  exposure =   1.0446921E+06
 Chip  5  backscale=   1.0673821E+08  exposure =   9.8330825E+05
 Chip  7  backscale=   1.1046149E+08  exposure =   1.0427332E+06
 Process the observation data from the corner regions
 /home/dbh/astrosoft/xmm-esas/ccf/mos1-qpb.fits.gz

 AUG_GET_EXP POSITION 03
 STATUS FTOPEN = 104
 /home/dbh/astrosoft/xmm-esas/ccf/mos1-qpb.fits.gz

 Rate:    4.3284424E-02  Rate error:  NaN
 Hard:    4.3148150  Hard error:  NaN
 Exposure:    0.0000000
 Exposure weighted count rate:  NaN
 Observation count rate:    4.3284424E-02  and correction scale factor:  NaN
 2   3.0503132E+07 NaN
 /home/dbh/astrosoft/xmm-esas/ccf/mos1-qpb.fits.gz
 AUG_GET_EXP POSITION 03
 STATUS FTOPEN = 104
 /home/dbh/astrosoft/xmm-esas/ccf/mos1-qpb.fits.gz
 Rate:    3.6651514E-02  Rate error:  NaN
 Hard:    5.6885247  Hard error:  NaN
 Exposure:    0.0000000
 Exposure weighted count rate:  NaN
 Observation count rate:    3.6651514E-02  and correction scale factor:  NaN
 3   2.8872112E+07 NaN
<truncated>


It seems that the problem is that it's looking for a file called
/home/dbh/astrosoft/xmm-esas/ccf/mos1-qpb.fits.gz, and no such file
exists in ESAS-CCF.tar (they're called mos1-2qpb.fits.gz,
mos1-3qpb.fits.gz, etc.).

Regards,

Dave


On Mon, May 24, 2010 at 07:46, Pedro M. Rodriguez Pascual
<xmmhelp@sciops.esa.int> wrote:
> David,
>
> Unfortunately, the actual origin of the problem reported has not yet been
fully
> understood. It has been found that the initialization of some parameters in
> calls to fitsio routines may lead to unexpected errors, but developers are
not
> completely sure that it is really the origin of the problem and, therefore,
are
> still analyzing the case.
>
> We will come back when further news are available.
>
> Sincerely,
>
> Pedro
>
>
> ================================================================================================
> This message and any attachments are intended for the use of the addressee
or addressees only.
>
> The unauthorised disclosure, use, dissemination or copying (either in whole
or in part) of its content is prohibited.
>
> If you received this message in error, please delete it from your system
and notify the sender.
>
> E-mails can be altered and their integrity cannot be guaranteed.
>
> ESA shall not be liable for any e-mail if modified.
> =================================================================================================
>
>
>



Reply 3

Resend
From: Pedro M. Rodriguez Pascual <xmmhelp@sciops.esa.int>
To: dbh@physast.uga.edu
Subject: Re: mos_back (PR#43949)
Date: Tue Aug 10 14:59:51 2010
Hello Dave,

thanks for the update. 

Unfortunately, the solution to the ESAS issues is taking longer than expected.

I have forwarded your message to SAS developer for it to be added to the
analysis. 

Sincerely,

Pedro

> Dear Pedro,
> 
> I've been working on other things recently, and have only just come
> back to looking at this problem.
> 
> The patched version of ESAS seems to have solved the problem that I
> originally reported. However, I'm now having similar problems to those
> reported by Terry Gaetz (SASv10.0/43944), in that mos_back is
> producing NaNs:
> 
>  xmmdir: /home/dbh/astrosoft/xmm-esas/ccf
> 
>  diag:  0
>  prefix: 1S001
>  mosnum:  1
>  obj_file: mos1S001-obj.pi
> 
>  obj_rmf: mos1S001.rmf
> 
>  el, eh:  0 0
>  CCD selection 1 1 1 0 1 0 1
>  WARNING: if chip 3, 4 or 6 are missing spurious
>  gold features can arise in the 2.04-2.33,
>  9.38-9.98, 11.03-11.82 keV regions
>  CalDB Directory: /home/dbh/astrosoft/xmm-esas/ccf
> 
>  mosnam 1
>  qpb_fi /mos1-qpb.fits.gz
>  CalDB QPB FIle: /home/dbh/astrosoft/xmm-esas/ccf/mos1-qpb.fits.gz
> 
>  Process the observation data
>  Backscale and exposure from the observation data
>  Chip  1  backscale=   1.6266296E+08  exposure =   5.0486500E+04
>  Chip  2  backscale=   1.0901646E+08  exposure =   5.0525281E+04
>  Chip  3  backscale=   6.0418408E+07  exposure =   5.0557254E+04
>  Chip  5  backscale=   1.0673821E+08  exposure =   5.0503758E+04
>  Chip  7  backscale=   1.1046149E+08  exposure =   5.0433355E+04
>  Process the FWC data from the object region
>  Backscale and exposure from the FWC data
>  Chip  1  backscale=   1.6187579E+08  exposure =   1.0300928E+06
>  Chip  2  backscale=   1.0778292E+08  exposure =   1.0444642E+06
>  Chip  3  backscale=   6.0418408E+07  exposure =   1.0446921E+06
>  Chip  5  backscale=   1.0673821E+08  exposure =   9.8330825E+05
>  Chip  7  backscale=   1.1046149E+08  exposure =   1.0427332E+06
>  Process the observation data from the corner regions
>  /home/dbh/astrosoft/xmm-esas/ccf/mos1-qpb.fits.gz
> 
>  AUG_GET_EXP POSITION 03
>  STATUS FTOPEN = 104
>  /home/dbh/astrosoft/xmm-esas/ccf/mos1-qpb.fits.gz
> 
>  Rate:    4.3284424E-02  Rate error:  NaN
>  Hard:    4.3148150  Hard error:  NaN
>  Exposure:    0.0000000
>  Exposure weighted count rate:  NaN
>  Observation count rate:    4.3284424E-02  and correction scale factor: 
NaN
>  2   3.0503132E+07 NaN
>  /home/dbh/astrosoft/xmm-esas/ccf/mos1-qpb.fits.gz
>  AUG_GET_EXP POSITION 03
>  STATUS FTOPEN = 104
>  /home/dbh/astrosoft/xmm-esas/ccf/mos1-qpb.fits.gz
>  Rate:    3.6651514E-02  Rate error:  NaN
>  Hard:    5.6885247  Hard error:  NaN
>  Exposure:    0.0000000
>  Exposure weighted count rate:  NaN
>  Observation count rate:    3.6651514E-02  and correction scale factor: 
NaN
>  3   2.8872112E+07 NaN
> <truncated>
> 
> 
> It seems that the problem is that it's looking for a file called
> /home/dbh/astrosoft/xmm-esas/ccf/mos1-qpb.fits.gz, and no such file
> exists in ESAS-CCF.tar (they're called mos1-2qpb.fits.gz,
> mos1-3qpb.fits.gz, etc.).
> 
> Regards,
> 
> Dave
> 
> 
> On Mon, May 24, 2010 at 07:46, Pedro M. Rodriguez Pascual
> <xmmhelp@sciops.esa.int> wrote:
>> David,
>>
>> Unfortunately, the actual origin of the problem reported has not yet
been
> fully
>> understood. It has been found that the initialization of some
parameters in
>> calls to fitsio routines may lead to unexpected errors, but developers
are
not
>> completely sure that it is really the origin of the problem and,
therefore,
> are
>> still analyzing the case.
>>
>> We will come back when further news are available.
>>
>> Sincerely,
>>
>> Pedro
>>
>>
>> ================================================================================================
>> This message and any attachments are intended for the use of the
addressee
or
> addressees only.
>>
>> The unauthorised disclosure, use, dissemination or copying (either in
whole
or
> in part) of its content is prohibited.
>>
>> If you received this message in error, please delete it from your
system and
> notify the sender.
>>
>> E-mails can be altered and their integrity cannot be guaranteed.
>>
>> ESA shall not be liable for any e-mail if modified.
>> =================================================================================================
>>
>>
>>
> 
> 


Reply 4

Resend
From: Pedro M. Rodriguez Pascual <xmmhelp@sciops.esa.int>
To: dbh@physast.uga.edu
Subject: Re: mos_back (PR#43949)
Date: Wed Aug 11 09:52:18 2010
Hello Dave,

The file mos1-qpb.fits.gz can be found in 

ftp://xmm.esac.esa.int/pub/ccf/constituents/extras/esas_caldb/

Will you please download all the files in this folder and try to run esas
again?

Pedro



Followup 2

Compose reply
Download message
Date: Fri, 13 Aug 2010 09:40:58 -0400
Subject: Re: mos_back (PR#43949)
From: David Henley <dbh@physast.uga.edu>
To: "Pedro M. Rodriguez Pascual" <xmmhelp@sciops.esa.int>
Hi Pedro,

mos_back now seems to be running fine. Many thanks for your help.

Regards,

Dave

On Wed, Aug 11, 2010 at 05:52, Pedro M. Rodriguez Pascual
<xmmhelp@sciops.esa.int> wrote:
> Hello Dave,
>
> The file mos1-qpb.fits.gz can be found in
>
> ftp://xmm.esac.esa.int/pub/ccf/constituents/extras/esas_caldb/
>
> Will you please download all the files in this folder and try to run esas
> again?
>
> Pedro
>
>
>
> ================================================================================================
> This message and any attachments are intended for the use of the addressee
or addressees only.
>
> The unauthorised disclosure, use, dissemination or copying (either in whole
or in part) of its content is prohibited.
>
> If you received this message in error, please delete it from your system
and notify the sender.
>
> E-mails can be altered and their integrity cannot be guaranteed.
>
> ESA shall not be liable for any e-mail if modified.
> =================================================================================================
>
>
>


Up to top level
AO15   AO16   AO17   AO18   Backgrounds   Calibration   Conference   Data   Docs   EPICMOS   EPICpn   Feedback   Gallery   Misc   OM   Pending   PhD_Theses   Publications   RGS   RadMonitor   SAS_Hardware   SAS_WS   SASv16.0   SASv16.0_Installation   SASv16.1   SASv16.1_Installation   SASv17.0   SASv17.0_Installation   SASv18.0   SASv18.0_Installation   SciSim   Simulators_other   Suggestions   Trash   Visibility   XMM-bouncing   XMM-news   XRPS   XSA   esas   incoming  

Logged in as guest


Please make your (short) question the subject of your request!


Web interface using JitterBug ... back to the XMM home page