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/48455
Full headers

From: paulgeringer2012@u.northwestern.edu
Subject: swcx bus error/segmentation fault
Compose reply
Download message
Move To:
3 replies: 1 2 3
1 followups: 1

Private message: yes  no

Notes:

Notification:


Date: Mon, 22 Aug 2011 05:33:17 GMT
From: paulgeringer2012@u.northwestern.edu
To: xmmhelp@sciops.esa.int
Cc: paulgeringer2012@u.northwestern.edu
Subject: swcx bus error/segmentation fault
Full_Name: Paul Geringer
Submission from: (NULL) (98.213.49.64)


I'm trying to run some final processing after making a spectral fit to generate
proton and swcx parameters. I've run mos/pn-spectra and mos/pn_back, and have
generated fitted values. However, I ran into an issue when trying to run the
swcx task.

For example:

bash-3.2$ swcx prefix=1S001 caldb=~/XMM/CCF ccd1=1 ccd2=1 ccd3=1 ccd4=1 ccd5=1
ccd6=1 ccd7=1 elow=400 ehigh=1250 linelist='1 2' gnormlist='7.58145E-07
5.45516E-08' objarf=mos1S001-full.arf objspec=mos1S001-obj-full.pi

Bus error

The directory ~/XMM/CCF/ contains the CCF data files and the updated esas
calibration files, including swcx-im.fits.gz file. All of the CCDs were included
in the mos-spectra/back tasks. The energy range is the also the same. Both the
objarf and objspec files exist. Running this task for the MOS2 observation
produces the same output and pn produces "Segmentation Fault" instead.
HEASOFT-6.10 has been initialized, SAS was started, and the SAS_ODF, SAS_CCF,
and SAS_CCFPATH environment variables have been set. 

This problem has occurred on multiple ObsIDs, such as 0204720101 and 0085590201.
I have not seen this problem on any other task, and proton, for example, works
as expected. 

Any assistance would be greatly appreciated. Thanks.


Reply 1

Resend
From: Ignacio de la Calle <xmmhelp@sciops.esa.int>
To: paulgeringer2012@u.northwestern.edu
Subject: Re: swcx bus error/segmentation fault (PR#48455)
Date: Tue Aug 23 09:16:01 2011
Dear Paul,

I have sent your email to the ESAS developer, but I would need some 
more information from you.

Could you send me the output of the calls:

  uname -a

  sasversion

Before the Bus error, do you get any other output information ?
Could you set the following variable,

 setenv SAS_VERBOSITY 5

to see if you get any more output information ? If so, send it to me.

Regards,

Ignacio de la Calle
XMM-Newton SOC



> Submission from: (NULL) (98.213.49.64)
> 
> 
> I'm trying to run some final processing after making a spectral fit to
generate
> proton and swcx parameters. I've run mos/pn-spectra and mos/pn_back, and
have
> generated fitted values. However, I ran into an issue when trying to run
the
> swcx task.
> 
> For example:
> 
> bash-3.2$ swcx prefix=1S001 caldb=~/XMM/CCF ccd1=1 ccd2=1 ccd3=1 ccd4=1
ccd5=1
> ccd6=1 ccd7=1 elow=400 ehigh=1250 linelist='1 2' gnormlist='7.58145E-07
> 5.45516E-08' objarf=mos1S001-full.arf objspec=mos1S001-obj-full.pi
> 
> Bus error
> 
> The directory ~/XMM/CCF/ contains the CCF data files and the updated esas
> calibration files, including swcx-im.fits.gz file. All of the CCDs were
included
> in the mos-spectra/back tasks. The energy range is the also the same. Both
the
> objarf and objspec files exist. Running this task for the MOS2 observation
> produces the same output and pn produces "Segmentation Fault" instead.
> HEASOFT-6.10 has been initialized, SAS was started, and the SAS_ODF,
SAS_CCF,
> and SAS_CCFPATH environment variables have been set. 
> 
> This problem has occurred on multiple ObsIDs, such as 0204720101 and
0085590201.
> I have not seen this problem on any other task, and proton, for example,
works
> as expected. 
> 
> Any assistance would be greatly appreciated. Thanks.
> 
> 


Followup 1

Compose reply
Download message
From: Paul Geringer <paulgeringer2012@u.northwestern.edu>
Date: Wed, 24 Aug 2011 01:21:37 -0500
Subject: Re: swcx bus error/segmentation fault (PR#48455)
To: Ignacio de la Calle <xmmhelp@sciops.esa.int>
--0016364eecba4849b404ab3a54cb
Content-Type: text/plain; charset=ISO-8859-1

This is the result for uname -a:

Darwin 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009;
root:xnu-1228.15.4~1/RELEASE_I386 i386

This is the result for sasversion:
sasversion:- XMM-Newton SAS release and build information:

SAS release: xmmsas_20110223_1803-11.0.0
Compiled on: Wed Feb 23 19:31:36 CET 2011
Compiled by: sasbuild@xmacserver
Platform   : Darwin-9.8.0 32

SAS-related environment variables that are set:

SAS_DIR = /Users/paulgeringer/XMM/xmmsas_20110223_1803
SAS_PATH = /Users/paulgeringer/XMM/xmmsas_20110223_1803

And here is the output for when I run the task with the verbosity set to 5:

swcx:- Executing (routine): swcx prefix=2S002 caldb=~XMM/CCF/
objarf=mos2S002-full.arf objspec=mos2S002-obj-full.pi ccd1=1 ccd2=1 ccd3=1
ccd4=1 ccd5=0 ccd6=1 ccd7=1 elow=400 ehigh=1250 gnormlist='7.58145e-07
5.45516e-08' linelist='1 2'  -V 5
swcx:- swcx (esas-0.9.15)  [xmmsas_20110223_1803-11.0.0] started:
 2011-08-24T06:15:15.000
Bus error

Last night I ran into a different error upon using a Linux machine instead.
I tried submitting it to my previous request as a note, but I don't think it
went through. I'm unsure if the issues are related, but just incase, here is
that message:

This was run on a Mac Pro running the most recent version of OS X 10.5. I
have tried this task on another computer running Linux, but ran into a
different error.

swcx prefix=2S002 caldb=~/CCF/ ccd1=1 ccd2=1 ccd3=1 ccd4=1 ccd5=0 ccd6=1
ccd7=1 elow=400 ehigh=1250 linelist='1 2' gnormlist='7.58145E-07
5.45516E-08' objarf=mos2S002-full.arf objspec=mos2S002-obj-full.pi
Runtime Error: subs.f, line 4548: Invalid reference to procedure READ_ARF -
Dummy argument OBJ_ARF has length 80 but actual argument length -931704048
is shorter
Program terminated by fatal error
Aborted

I then ran the following command accidentally:

swcx prefix=2S002 caldb=~/CCF/ ccd1=1 ccd2=1 ccd3=1 ccd4=1 ccd5=0 ccd6=1
ccd7=1 elow=400 ehigh=1250 linelist='1 2' gnormlist='7.58145E-07
5.45516E-08' objarf=pnS003-full.arf objspec=pnS003-obj-full.pi
 xmmdir: /home/paulg/CCF/

 prefix: 2S002
 CCD selection 1 1 1 1 1 1 1
 elow, ehigh:  400 1250
 idet:  2
 Line and Norm:  1   OVII     7.5814501E-07
 Line and Norm:  2   OVIII    5.4551599E-08
 /home/paulg/CCF//swcx-im.fits.gz

 7 OVII
 M2OVII
 Total SWCX counts from OVII  :    1.4209198E+03
 8 OVIII
 M2OVIII
 Total SWCX counts from OVIII :    1.1913845E+02
 Total SWCX counts in band:    1.5395549E+03
 Template image
 mos2S002-obj-im-det-400-1250.fits

 Output file name
 mos2S002-swcx-im-det-400-1250.fits

This ran on the 2S002 exposure, yet the objspec and objarf files were
incorrectly set to the pnS003 exposure.

I assume this means that my previous issue is a Mac related issue, but I
can't figure out how to fix this new issue.

~Paul G.

On Tue, Aug 23, 2011 at 4:16 AM, Ignacio de la Calle <xmmhelp@sciops.esa.int
> wrote:

> Dear Paul,
>
> I have sent your email to the ESAS developer, but I would need some
> more information from you.
>
> Could you send me the output of the calls:
>
>  uname -a
>
>  sasversion
>
> Before the Bus error, do you get any other output information ?
> Could you set the following variable,
>
>  setenv SAS_VERBOSITY 5
>
> to see if you get any more output information ? If so, send it to me.
>
> Regards,
>
> Ignacio de la Calle
> XMM-Newton SOC
>
>
>
> > Submission from: (NULL) (98.213.49.64)
> >
> >
> > I'm trying to run some final processing after making a spectral fit to
> generate
> > proton and swcx parameters. I've run mos/pn-spectra and mos/pn_back,
and
> have
> > generated fitted values. However, I ran into an issue when trying to
run
> the
> > swcx task.
> >
> > For example:
> >
> > bash-3.2$ swcx prefix=1S001 caldb=~/XMM/CCF ccd1=1 ccd2=1 ccd3=1
ccd4=1
> ccd5=1
> > ccd6=1 ccd7=1 elow=400 ehigh=1250 linelist='1 2'
gnormlist='7.58145E-07
> > 5.45516E-08' objarf=mos1S001-full.arf objspec=mos1S001-obj-full.pi
> >
> > Bus error
> >
> > The directory ~/XMM/CCF/ contains the CCF data files and the updated
esas
> > calibration files, including swcx-im.fits.gz file. All of the CCDs
were
> included
> > in the mos-spectra/back tasks. The energy range is the also the same.
> Both
> the
> > objarf and objspec files exist. Running this task for the MOS2
> observation
> > produces the same output and pn produces "Segmentation Fault" instead.
> > HEASOFT-6.10 has been initialized, SAS was started, and the SAS_ODF,
> SAS_CCF,
> > and SAS_CCFPATH environment variables have been set.
> >
> > This problem has occurred on multiple ObsIDs, such as 0204720101 and
> 0085590201.
> > I have not seen this problem on any other task, and proton, for
example,
> w

Message of length 16034 truncated


Reply 2

Resend
From: Ignacio de la Calle <xmmhelp@sciops.esa.int>
To: paulgeringer2012@u.northwestern.edu
Subject: Re: swcx bus error/segmentation fault (PR#48455)
Date: Wed Aug 24 10:11:45 2011
Dear Paul,

Many thanks for the information. I have passed your emails to the ESAS
developer
and informed him about the problem you have. Unfortunately he is on leave until
August 30th, so I wont be able to come back to you with an answer before then.
In the meantime I will try and see if I can reproduce the error and come up
with
an answer before then.

Regards,

Ignacio de la Calle
XMM-Newton SOC


Reply 3

Resend
From: Ignacio de la Calle <xmmhelp@sciops.esa.int>
To: paulgeringer2012@u.northwestern.edu
Subject: Re: swcx bus error/segmentation fault (PR#48455)
Date: Mon Aug 26 09:42:55 2013
Dear Paul,

During a recent general review of helpdesk tickets, I have come across
this very old one. I am aware that my reply is very late. I just wanted
to apologize for letting this slip through. I got a very late reply from
the ESAS developer which I never passed on to you. You have probably 
already solved the problem and are even working with a more recent
version of SAS.

Once again, apologies for my late reply and please let me know if I can 
be of further help.

Regards,

Ignacio de la Calle
XMM-Newton SOC

> Content-Type: text/plain; charset=ISO-8859-1
> 
> This is the result for uname -a:
> 
> Darwin 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009;
> root:xnu-1228.15.4~1/RELEASE_I386 i386
> 
> This is the result for sasversion:
> sasversion:- XMM-Newton SAS release and build information:
> 
> SAS release: xmmsas_20110223_1803-11.0.0
> Compiled on: Wed Feb 23 19:31:36 CET 2011
> Compiled by: sasbuild@xmacserver
> Platform   : Darwin-9.8.0 32
> 
> SAS-related environment variables that are set:
> 
> SAS_DIR = /Users/paulgeringer/XMM/xmmsas_20110223_1803
> SAS_PATH = /Users/paulgeringer/XMM/xmmsas_20110223_1803
> 
> And here is the output for when I run the task with the verbosity set to
5:
> 
> swcx:- Executing (routine): swcx prefix=2S002 caldb=~XMM/CCF/
> objarf=mos2S002-full.arf objspec=mos2S002-obj-full.pi ccd1=1 ccd2=1 ccd3=1
> ccd4=1 ccd5=0 ccd6=1 ccd7=1 elow=400 ehigh=1250 gnormlist='7.58145e-07
> 5.45516e-08' linelist='1 2'  -V 5
> swcx:- swcx (esas-0.9.15)  [xmmsas_20110223_1803-11.0.0] started:
>  2011-08-24T06:15:15.000
> Bus error
> 
> Last night I ran into a different error upon using a Linux machine
instead.
> I tried submitting it to my previous request as a note, but I don't think
it
> went through. I'm unsure if the issues are related, but just incase, here
is
> that message:
> 
> This was run on a Mac Pro running the most recent version of OS X 10.5. I
> have tried this task on another computer running Linux, but ran into a
> different error.
> 
> swcx prefix=2S002 caldb=~/CCF/ ccd1=1 ccd2=1 ccd3=1 ccd4=1 ccd5=0 ccd6=1
> ccd7=1 elow=400 ehigh=1250 linelist='1 2' gnormlist='7.58145E-07
> 5.45516E-08' objarf=mos2S002-full.arf objspec=mos2S002-obj-full.pi
> Runtime Error: subs.f, line 4548: Invalid reference to procedure READ_ARF
-
> Dummy argument OBJ_ARF has length 80 but actual argument length -931704048
> is shorter
> Program terminated by fatal error
> Aborted
> 
> I then ran the following command accidentally:
> 
> swcx prefix=2S002 caldb=~/CCF/ ccd1=1 ccd2=1 ccd3=1 ccd4=1 ccd5=0 ccd6=1
> ccd7=1 elow=400 ehigh=1250 linelist='1 2' gnormlist='7.58145E-07
> 5.45516E-08' objarf=pnS003-full.arf objspec=pnS003-obj-full.pi
>  xmmdir: /home/paulg/CCF/
> 
>  prefix: 2S002
>  CCD selection 1 1 1 1 1 1 1
>  elow, ehigh:  400 1250
>  idet:  2
>  Line and Norm:  1   OVII     7.5814501E-07
>  Line and Norm:  2   OVIII    5.4551599E-08
>  /home/paulg/CCF//swcx-im.fits.gz
> 
>  7 OVII
>  M2OVII
>  Total SWCX counts from OVII  :    1.4209198E+03
>  8 OVIII
>  M2OVIII
>  Total SWCX counts from OVIII :    1.1913845E+02
>  Total SWCX counts in band:    1.5395549E+03
>  Template image
>  mos2S002-obj-im-det-400-1250.fits
> 
>  Output file name
>  mos2S002-swcx-im-det-400-1250.fits
> 
> This ran on the 2S002 exposure, yet the objspec and objarf files were
> incorrectly set to the pnS003 exposure.
> 
> I assume this means that my previous issue is a Mac related issue, but I
> can't figure out how to fix this new issue.
> 
> ~Paul G.
> 
> On Tue, Aug 23, 2011 at 4:16 AM, Ignacio de la Calle
<xmmhelp@sciops.esa.int
>> wrote:
> 
>> Dear Paul,
>>
>> I have sent your email to the ESAS developer, but I would need some
>> more information from you.
>>
>> Could you send me the output of the calls:
>>
>>  uname -a
>>
>>  sasversion
>>
>> Before the Bus error, do you get any other output information ?
>> Could you set the following variable,
>>
>>  setenv SAS_VERBOSITY 5
>>
>> to see if you get any more output information ? If so, send it to me.
>>
>> Regards,
>>
>> Ignacio de la Calle
>> XMM-Newton SOC
>>
>>
>>
>> > Submission from: (NULL) (98.213.49.64)
>> >
>> >
>> > I'm trying to run some final processing after making a spectral
fit to
>> generate
>> > proton and swcx parameters. I've run mos/pn-spectra and
mos/pn_back, and
>> have
>> > generated fitted values. However, I ran into an

Message of length 18432 truncated

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