Up to top level
AO15   AO16   AO17   AO18   AO19   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/48606
Full headers

From: ozden sengul <ozden@juno.phys.s.u-tokyo.ac.jp>
Subject: mos-back_segmentation fault
Compose reply
Download message
Move To:
2 replies: 1 2
2 followups: 1 2

Private message: yes  no

Notes:

Notification:


Date: Sun, 11 Sep 2011 12:44:55 +0900
Subject: mos-back_segmentation fault
From: ozden sengul <ozden@juno.phys.s.u-tokyo.ac.jp>
To: "Pedro M. Rodriguez Pascual" <xmmhelp@sciops.esa.int>
--bcaec5215f55dea3bd04aca23b13
Content-Type: text/plain; charset=ISO-8859-1

Hi!

I again met the problem "segmentation fault" while trying to create
mos-back.
The input and output is as below:
How can I solve this problem?

p25044-ipngn3301marunouchi:r_0.5 sengulozden$ mos_back prefix=1S001
caldb=/usr/bin/SAS/ccf diag=0 elow=400 ehigh=12000 ccd1=1 ccd2=1 ccd3=1
ccd4=1 ccd5=0 ccd6=1 ccd7=1
 xmmdir: /usr/bin/SAS/ccf

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

 obj_rmf: mos1S001.rmf

 el, eh:  400 12000
 CCD selection 1 1 1 1 0 1 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
 Observation took place after MOS1 CCD6 was lost
 Set ccd(6) equal to 0
 Revised CCD selection
 CCD selection 1 1 1 1 0 0 1
 CalDB Directory: /usr/bin/SAS/ccf

 mosnam 1
 qpb_fi /mos1-qpb.fits.gz
 CalDB QPB FIle: /usr/bin/SAS/ccf/mos1-qpb.fits.gz

 Process the observation data
 READ_PHA POSITION 11
 Missing EXPOSURE keyword
 Missing file: mos1S001-2obj.pi

      in XMM_BACK, noted on return from READ_PHA
 READ_PHA POSITION 11
 Missing EXPOSURE keyword
 Missing file: mos1S001-3obj.pi

      in XMM_BACK, noted on return from READ_PHA
 READ_PHA POSITION 11
 Missing EXPOSURE keyword
 Missing file: mos1S001-4obj.pi

      in XMM_BACK, noted on return from READ_PHA
 READ_PHA POSITION 11
 Missing EXPOSURE keyword
 Missing file: mos1S001-7obj.pi

      in XMM_BACK, noted on return from READ_PHA
 Backscale and exposure from the observation data
 Chip  1  backscale=   8.1120000E+05  exposure =   8.7604014E+03
 Chip  2  backscale=   0.0000000  exposure =   0.0000000
 Chip  3  backscale=   0.0000000  exposure =   0.0000000
 Chip  4  backscale=   0.0000000  exposure =   0.0000000
 Chip  7  backscale=   0.0000000  exposure =   0.0000000
 Process the FWC data from the object region
 READ_PHA POSITION 11
 Missing EXPOSURE keyword
 READ_PHA POSITION 11
 Missing EXPOSURE keyword
 READ_PHA POSITION 11
 Missing EXPOSURE keyword
 READ_PHA POSITION 11
 Missing EXPOSURE keyword
 Backscale and exposure from the FWC data
 Chip  1  backscale=   8.1600000E+05  exposure =   1.6105479E+06
 Chip  2  backscale=   0.0000000  exposure =   1.6105479E+06
 Chip  3  backscale=   0.0000000  exposure =   1.6105479E+06
 Chip  4  backscale=   0.0000000  exposure =   1.6105479E+06
 Chip  7  backscale=   0.0000000  exposure =   1.6105479E+06
 Process the observation data from the corner regions
 /usr/bin/SAS/ccf/mos1-qpb.fits.gz

 AUG_GET_EXP POSITION 03
 STATUS FTOPEN = 104
 /usr/bin/SAS/ccf/mos1-qpb.fits.gz

Segmentation fault

--bcaec5215f55dea3bd04aca23b13
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi!<div><br></div><div>I again met the problem
&quot;segmentation fault&quo=
t; while trying to create mos-back.</div><div>The input and output
is as be=
low:</div><div>How can I solve this
problem?</div><div><br></div><div><div>
p25044-ipngn3301marunouchi:r_0.5 sengulozden$ mos_back prefix=3D1S001 caldb=
=3D/usr/bin/SAS/ccf diag=3D0 elow=3D400 ehigh=3D12000 ccd1=3D1 ccd2=3D1 ccd=
3=3D1 ccd4=3D1 ccd5=3D0 ccd6=3D1 ccd7=3D1</div><div>=A0xmmdir:
/usr/bin/SAS=
/ccf =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0</div>
<div>=A0diag: =A00</div><div>=A0prefix:
1S001</div><div>=A0mosnum: =A01</di=
v><div>=A0obj_file: mos1S001-obj.pi =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0=A0</div><div>=A0obj_rmf: mos1S001.rmf =A0 =A0 =A0
=A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0</div>
<div>=A0el, eh: =A0400 12000</div><div>=A0CCD selection 1 1 1
1 0 1 1</div>=
<div>=A0WARNING: if chip 3, 4 or 6 are missing
spurious=A0</div><div>=A0gol=
d features can arise in the 2.04-2.33,=A0</div><div>=A09.38-9.98,
11.03-11.=
82 keV regions</div>
<div>=A0Observation took place after MOS1 CCD6 was
lost</div><div>=A0Set cc=
d(6) equal to 0</div><div>=A0Revised CCD
selection=A0</div><div>=A0CCD sele=
ction 1 1 1 1 0 0 1</div><div>=A0CalDB Directory: /usr/bin/SAS/ccf
=A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0</div>
<div>=A0mosnam 1</div><div>=A0qpb_fi /mos1-qpb.fits.gz =A0 =A0
=A0 =A0</div=
><div>=A0CalDB QPB FIle: /usr/bin/SAS/ccf/mos1-qpb.fits.gz =A0 =A0 =A0
=A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
=A0</div><div>=A0Process the observation
data</div><div>

Message of length 8682 truncated

Reply 1

Resend
From: Matthias Ehle <xmmhelp@sciops.esa.int>
To: ozden@juno.phys.s.u-tokyo.ac.jp
Subject: Re: mos-back_segmentation fault (PR#48606)
Date: Tue Sep 13 11:34:51 2011
Dear Ozden,

I had a look at other ESAS related helpdesk questions and see that
sometimes such problems were found to be related to a not clean SAS
installation (several versions) or not updated calibration files (e.g.
if you downloaded SAS v11 before March 24, 2011, you should update your 
esas-caldb according to the content of 
ftp://xmm.esac.esa.int/pub/ccf/constituents/extras/esas_caldb/ )
It might be useful to install SAS and cal. files from scratch...

ESAS is a very large software package that does many things, hence it is a bit
complicated for me to track down your problem and to check if it is
related to your installation or actually to ESAS.

If you let me know which observation you are trying to analyse and the steps
you did before the fault, I could at least check if I can do the process
here in our environment. Before doing so:

I see that a similar problem was reported by another user that triggered
a colleague of mine doing the analysis here (succesfully) - you can check his
produced files and logs:

(ESAS was run up to pn_back and mos_back).

at   ftp://ftp.sciops.esa.int/pub/icalle/ESAS/
where you will see 3 files:

1. analysis_steps.log: contains a list of all the steps followed. Included 
   at the end the list of files present in our ESAS CALDB directory.

2. logs.tar: contains all the log files from all the ESAS tasks listed in
   analysis_steps.log. At the end of every log we have also included a list
   of all the files produced by the task.

3. files.tar.gz: in case you are interested, we have placed all the files 
   generated by SAS and ESAS tasks in this tar files.

You could also try, if possible for you, to process your data with the SAS
insatlled in a different operating system; sometimes the MAC OS has issues
that we do not see on other platforms.

We ope this info helps you to proceed with your analysis.

Regards,
   Matthias

> 
> Hi!
> 
> I again met the problem "segmentation fault" while trying to create
> mos-back.
> The input and output is as below:
> How can I solve this problem?
> 
> p25044-ipngn3301marunouchi:r_0.5 sengulozden$ mos_back prefix=1S001
> caldb=/usr/bin/SAS/ccf diag=0 elow=400 ehigh=12000 ccd1=1 ccd2=1 ccd3=1
> ccd4=1 ccd5=0 ccd6=1 ccd7=1
>  xmmdir: /usr/bin/SAS/ccf
> 
>  diag:  0
>  prefix: 1S001
>  mosnum:  1
>  obj_file: mos1S001-obj.pi
> 
>  obj_rmf: mos1S001.rmf
> 
>  el, eh:  400 12000
>  CCD selection 1 1 1 1 0 1 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
>  Observation took place after MOS1 CCD6 was lost
>  Set ccd(6) equal to 0
>  Revised CCD selection
>  CCD selection 1 1 1 1 0 0 1
>  CalDB Directory: /usr/bin/SAS/ccf
> 
>  mosnam 1
>  qpb_fi /mos1-qpb.fits.gz
>  CalDB QPB FIle: /usr/bin/SAS/ccf/mos1-qpb.fits.gz
> 
>  Process the observation data
>  READ_PHA POSITION 11
>  Missing EXPOSURE keyword
>  Missing file: mos1S001-2obj.pi
> 
>       in XMM_BACK, noted on return from READ_PHA
>  READ_PHA POSITION 11
>  Missing EXPOSURE keyword
>  Missing file: mos1S001-3obj.pi
> 
>       in XMM_BACK, noted on return from READ_PHA
>  READ_PHA POSITION 11
>  Missing EXPOSURE keyword
>  Missing file: mos1S001-4obj.pi
> 
>       in XMM_BACK, noted on return from READ_PHA
>  READ_PHA POSITION 11
>  Missing EXPOSURE keyword
>  Missing file: mos1S001-7obj.pi
> 
>       in XMM_BACK, noted on return from READ_PHA
>  Backscale and exposure from the observation data
>  Chip  1  backscale=   8.1120000E+05  exposure =   8.7604014E+03
>  Chip  2  backscale=   0.0000000  exposure =   0.0000000
>  Chip  3  backscale=   0.0000000  exposure =   0.0000000
>  Chip  4  backscale=   0.0000000  exposure =   0.0000000
>  Chip  7  backscale=   0.0000000  exposure =   0.0000000
>  Process the FWC data from the object region
>  READ_PHA POSITION 11
>  Missing EXPOSURE keyword
>  READ_PHA POSITION 11
>  Missing EXPOSURE keyword
>  READ_PHA POSITION 11
>  Missing EXPOSURE keyword
>  READ_PHA POSITION 11
>  Missing EXPOSURE keyword
>  Backscale and exposure from the FWC data
>  Chip  1  backscale=   8.1600000E+05  exposure =   1.6105479E+06
>  Chip  2  backscale=   0.0000000  exposure =   1.6105479E+06
>  Chip  3  backscale=   0.0000000  exposure =   1.6105479E+06
>  Chip  4  backscale=   0.0000000  exposure =   1.6105479E+06
>  Chip  7  backscale=   0.0000000  exposure =   1.6105479E+06
>  Process the observation data from the corner regions
>  /usr/bin/SAS/ccf/mos1-qpb.fits.gz
> 
>  AUG_GET_EXP POSITION 03
>  STATUS FTOPEN = 104
>  /usr/bin/SAS/ccf/mos1-qpb.fits.gz
> 
> Segmentation fault
> 


Followup 1

Compose reply
Download message
Subject: Re: mos-back_segmentation fault (PR#48606)
From: Ozden Sengul <ozden@juno.phys.s.u-tokyo.ac.jp>
Date: Thu, 15 Sep 2011 18:42:12 +0900
Cc: Ozden Sengul <ozden@juno.phys.s.u-tokyo.ac.jp>
To: Matthias Ehle <xmmhelp@sciops.esa.int>
Thank you very much for your e-mail and explanation.


I haven't corrected my calibration files yet, but I will start next week. If I
have problem, I will ask you again. I am currently studying Abell 2147 data. 

Best regards

On Sep 13, 2011, at 8:34 PM, Matthias Ehle wrote:

> Dear Ozden,
> 
> I had a look at other ESAS related helpdesk questions and see that
> sometimes such problems were found to be related to a not clean SAS
> installation (several versions) or not updated calibration files (e.g.
> if you downloaded SAS v11 before March 24, 2011, you should update your 
> esas-caldb according to the content of 
> ftp://xmm.esac.esa.int/pub/ccf/constituents/extras/esas_caldb/ )
> It might be useful to install SAS and cal. files from scratch...
> 
> ESAS is a very large software package that does many things, hence it is a
bit
> complicated for me to track down your problem and to check if it is
> related to your installation or actually to ESAS.
> 
> If you let me know which observation you are trying to analyse and the
steps
> you did before the fault, I could at least check if I can do the process
> here in our environment. Before doing so:
> 
> I see that a similar problem was reported by another user that triggered
> a colleague of mine doing the analysis here (succesfully) - you can check
his
> produced files and logs:
> 
> (ESAS was run up to pn_back and mos_back).
> 
> at   ftp://ftp.sciops.esa.int/pub/icalle/ESAS/
> where you will see 3 files:
> 
> 1. analysis_steps.log: contains a list of all the steps followed. Included 
>   at the end the list of files present in our ESAS CALDB directory.
> 
> 2. logs.tar: contains all the log files from all the ESAS tasks listed in
>   analysis_steps.log. At the end of every log we have also included a list
>   of all the files produced by the task.
> 
> 3. files.tar.gz: in case you are interested, we have placed all the files 
>   generated by SAS and ESAS tasks in this tar files.
> 
> You could also try, if possible for you, to process your data with the SAS
> insatlled in a different operating system; sometimes the MAC OS has issues
> that we do not see on other platforms.
> 
> We ope this info helps you to proceed with your analysis.
> 
> Regards,
>   Matthias
> 
>> 
>> Hi!
>> 
>> I again met the problem "segmentation fault" while trying to create
>> mos-back.
>> The input and output is as below:
>> How can I solve this problem?
>> 
>> p25044-ipngn3301marunouchi:r_0.5 sengulozden$ mos_back prefix=1S001
>> caldb=/usr/bin/SAS/ccf diag=0 elow=400 ehigh=12000 ccd1=1 ccd2=1 ccd3=1
>> ccd4=1 ccd5=0 ccd6=1 ccd7=1
>> xmmdir: /usr/bin/SAS/ccf
>> 
>> diag:  0
>> prefix: 1S001
>> mosnum:  1
>> obj_file: mos1S001-obj.pi
>> 
>> obj_rmf: mos1S001.rmf
>> 
>> el, eh:  400 12000
>> CCD selection 1 1 1 1 0 1 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
>> Observation took place after MOS1 CCD6 was lost
>> Set ccd(6) equal to 0
>> Revised CCD selection
>> CCD selection 1 1 1 1 0 0 1
>> CalDB Directory: /usr/bin/SAS/ccf
>> 
>> mosnam 1
>> qpb_fi /mos1-qpb.fits.gz
>> CalDB QPB FIle: /usr/bin/SAS/ccf/mos1-qpb.fits.gz
>> 
>> Process the observation data
>> READ_PHA POSITION 11
>> Missing EXPOSURE keyword
>> Missing file: mos1S001-2obj.pi
>> 
>>      in XMM_BACK, noted on return from READ_PHA
>> READ_PHA POSITION 11
>> Missing EXPOSURE keyword
>> Missing file: mos1S001-3obj.pi
>> 
>>      in XMM_BACK, noted on return from READ_PHA
>> READ_PHA POSITION 11
>> Missing EXPOSURE keyword
>> Missing file: mos1S001-4obj.pi
>> 
>>      in XMM_BACK, noted on return from READ_PHA
>> READ_PHA POSITION 11
>> Missing EXPOSURE keyword
>> Missing file: mos1S001-7obj.pi
>> 
>>      in XMM_BACK, noted on return from READ_PHA
>> Backscale and exposure from the observation data
>> Chip  1  backscale=   8.1120000E+05  exposure =   8.7604014E+03
>> Chip  2  backscale=   0.0000000  exposure =   0.0000000
>> Chip  3  backscale=   0.0000000  exposure =   0.0000000
>> Chip  4  backscale=   0.0000000  exposure =   0.0000000
>> Chip  7  backscale=   0.0000000  exposure =   0.0000000
>> Process the FWC data from the object region
>> READ_PHA POSITION 11
>> Missing EXPOSURE keyword
>> READ_PHA POSITION 11
>> Missing EXPOSURE keyword
>> READ_PHA POSITION 11
>> Missing EXPOSURE keyword
>> READ_PHA POSITION 11
>> Missing EXPOSURE keyword
>> Backscale and exposur

Message of length 6373 truncated


Followup 2

Compose reply
Download message
From: Ozden Sengul <ozden@juno.phys.s.u-tokyo.ac.jp>
To: Matthias Ehle <xmmhelp@sciops.esa.int>
Subject: Re: mos-back_segmentation fault (PR#48606)
Date: Wed, 21 Sep 2011 13:21:22 +0900
I began my analysis in the view of the file you sent to me, Although I  
am using the correct calibration files, I can not create mos-back and  
pn-back file. Error is

aoi:ODF ozden$ mos_back prefix=2S002 caldb=/Users/ozden/Desktop/ 
esas_caldb diag=0 elow=400 ehigh=12000 ccd1=1 ccd2=1 ccd3=1 ccd4=1  
ccd5=1 ccd6=1 ccd7=1
  xmmdir: /Users/ozden/Desktop/esas_caldb
  diag:  0
  prefix: 2S002
  mosnum:  2
  obj_file: mos2S002-obj.pi
  obj_rmf: mos2S002.rmf
  el, eh:  400 12000
  CCD selection 1 1 1 1 1 1 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: /Users/ozden/Desktop/esas_caldb
  mosnam 2
  qpb_fi /mos1-qpb.fits.gz
  CalDB QPB FIle: /Users/ozden/Desktop/esas_caldb/mos2-qpb.fits.gz
  Process the observation data
  Backscale and exposure from the observation data
  Chip  1  backscale=   1.6683965E+08  exposure =   8.4174326E+03
  Chip  2  backscale=   5.8898668E+07  exposure =   8.4158643E+03
  Chip  3  backscale=   8.1125376E+07  exposure =   8.4208516E+03
  Chip  4  backscale=   5.7287932E+07  exposure =   8.4287012E+03
  Chip  5  backscale=   5.9797076E+07  exposure =   8.4256064E+03
  Chip  6  backscale=   8.8205504E+07  exposure =   8.4207256E+03
  Chip  7  backscale=   6.2051716E+07  exposure =   8.4198359E+03
  Process the FWC data from the object region
  Backscale and exposure from the FWC data
  Chip  1  backscale=   1.6683965E+08  exposure =   1.5862148E+06
  Chip  2  backscale=   5.8898668E+07  exposure =   1.5859594E+06
  Chip  3  backscale=   8.1125376E+07  exposure =   1.5864754E+06
  Chip  4  backscale=   5.7287932E+07  exposure =   1.5878429E+06
  Chip  5  backscale=   5.9797076E+07  exposure =   1.5874138E+06
  Chip  6  backscale=   8.8198512E+07  exposure =   1.5867156E+06
  Chip  7  backscale=   6.2051716E+07  exposure =   1.5865678E+06
  Process the observation data from the corner regions
  /Users/ozden/Desktop/esas_caldb/mos2-qpb.fits.gz
  AUG_GET_EXP POSITION 05
  QUIES_CHIP2
  This was supposed to be the QPB 2  ext

On Sep 13, 2011, at 8:34 PM, Matthias Ehle wrote:

> Dear Ozden,
>
> I had a look at other ESAS related helpdesk questions and see that
> sometimes such problems were found to be related to a not clean SAS
> installation (several versions) or not updated calibration files (e.g.
> if you downloaded SAS v11 before March 24, 2011, you should update  
> your
> esas-caldb according to the content of
> ftp://xmm.esac.esa.int/pub/ccf/constituents/extras/esas_caldb/ )
> It might be useful to install SAS and cal. files from scratch...
>
> ESAS is a very large software package that does many things, hence  
> it is a bit
> complicated for me to track down your problem and to check if it is
> related to your installation or actually to ESAS.
>
> If you let me know which observation you are trying to analyse and  
> the steps
> you did before the fault, I could at least check if I can do the  
> process
> here in our environment. Before doing so:
>
> I see that a similar problem was reported by another user that  
> triggered
> a colleague of mine doing the analysis here (succesfully) - you can  
> check his
> produced files and logs:
>
> (ESAS was run up to pn_back and mos_back).
>
> at   ftp://ftp.sciops.esa.int/pub/icalle/ESAS/
> where you will see 3 files:
>
> 1. analysis_steps.log: contains a list of all the steps followed.  
> Included
>   at the end the list of files present in our ESAS CALDB directory.
>
> 2. logs.tar: contains all the log files from all the ESAS tasks  
> listed in
>   analysis_steps.log. At the end of every log we have also included  
> a list
>   of all the files produced by the task.
>
> 3. files.tar.gz: in case you are interested, we have placed all the  
> files
>   generated by SAS and ESAS tasks in this tar files.
>
> You could also try, if possible for you, to process your data with  
> the SAS
> insatlled in a different operating system; sometimes the MAC OS has  
> issues
> that we do not see on other platforms.
>
> We ope this info helps you to proceed with your analysis.
>
> Regards,
>   Matthias
>
>>
>> Hi!
>>
>> I again met the problem "segmentation fault" while trying to create
>> mos-back.
>> The input and output is as below:
>> How can I solve this problem?
>>
>> p25044-ipngn3301marunouchi:r_0.5 sengulozden$ mos_back prefix=1S001
>> caldb=/usr/bin/SAS/ccf diag=0 elow=400 ehigh=12000 ccd1=1 ccd2=1  
>> ccd3=1
>> ccd4=1 ccd5=0 ccd6=1 ccd7=1
>> xmmdir: /usr/bin/SAS/ccf
>>
>> diag:  0
>> prefix: 1S001
>> mosnum:  1
>> obj_file: mos1S001-obj.pi
>>
>> obj_rmf: mos1S001.rmf
>>
>> el, eh:  400 12000
>> CCD selection 1 1 1 1 0 1 1
>> 

Message of length 8832 truncated


Reply 2

Resend
From: Matthias Ehle <xmmhelp@sciops.esa.int>
To: ozden@juno.phys.s.u-tokyo.ac.jp
Subject: Re: mos-back_segmentation fault (PR#48606)
Date: Wed Sep 21 07:22:58 2011
Dear Ozden,

I actually have no clue...

Can you, please, re-submit this ticket to the NASA Guest Observer HelpDesk
(xmmhelp@athena.gsfc.nasa.gov). I think for this issue the advise from the
ESAS developers is needed.

Sorry that I have no further advice to offer here.

Cheers,
  Matthias

Up to top level
AO15   AO16   AO17   AO18   AO19   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