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   SciSim   Simulators_other   Suggestions   Trash   Visibility   XMM-bouncing   XMM-news   XRPS   XSA   esas   incoming  

Logged in as guest

Viewing EPICMOS/9156
Full headers

From: buote@uci.edu
Subject: emchain crashes on brand new data set
Compose reply
Download message
Move To:
2 replies: 1 2
2 followups: 1 2

Private message: yes  no

Notes:

Notification:


Date: Mon, 15 Sep 2003 18:08:26 GMT
From: buote@uci.edu
To: xmmhelp@xmm.vilspa.esa.es
Subject: emchain crashes on brand new data set
Name: David Buote

Email_Address: buote@uci.edu

Topic: tasks

Other_Topic: 

Usage_Mode: command line

SAS_Release: xmmsas_20030110_1802 - aka 5.4.1

Task_Version: emchain/epchain

Type: report a showstopper

Title: emchain crashes on brand new data set

Description: Hello,

I recently retrieved a new observation from the ftp site
at GSFC. Unfortunately, emchain crashes right at the beginning. It does not
behave this way for any of my other data sets, including another AO2
observation. I list the 
output below.

Thanks for any help,
David Buote

MOS: Running emchain...
Options passed to individual tasks:  -w 10 |
withbadpixfind = yes |
ODF directory = ../odf/
 
List of files in working directory :
0659_0151490101_PNS00301IME.FIT ... not M1 M2
0659_0151490101_PNS00302IME.FIT ... not M1 M2
0659_0151490101_PNS00303IME.FIT ... not M1 M2
0659_0151490101_PNS00304IME.FIT ... not M1 M2
0659_0151490101_PNS00305IME.FIT ... not M1 M2
0659_0151490101_PNS00306IME.FIT ... not M1 M2
0659_0151490101_PNS00307IME.FIT ... not M1 M2
0659_0151490101_PNS00308IME.FIT ... not M1 M2
0659_0151490101_R1S00409SPE.FIT ... not M1 M2
0659_0151490101_R2S00501SPE.FIT ... not M1 M2
0659_0151490101_R2S00502SPE.FIT ... not M1 M2
0659_0151490101_R2S00503SPE.FIT ... not M1 M2
0659_0151490101_R2S00505SPE.FIT ... not M1 M2
0659_0151490101_R2S00506SPE.FIT ... not M1 M2
0659_0151490101_R2S00507SPE.FIT ... not M1 M2
0659_0151490101_R2S00508SPE.FIT ... not M1 M2
0659_0151490101_R2S00509SPE.FIT ... not M1 M2
0659_0151490101_PNS00309IME.FIT ... not M1 M2
0659_0151490101_M1S00110IME.FIT ... OK
0659_0151490101_M1S00120IME.FIT ... OK
0659_0151490101_M1S00130IME.FIT ... OK
0659_0151490101_M1S00140IME.FIT ... OK
0659_0151490101_M1S00150IME.FIT ... OK
0659_0151490101_M1S00160IME.FIT ... OK
0659_0151490101_M1S00170IME.FIT ... OK
0659_0151490101_M2S00210IME.FIT ... OK
0659_0151490101_M2S00220IME.FIT ... OK
0659_0151490101_M2S00230IME.FIT ... OK
0659_0151490101_M2S00240IME.FIT ... OK
0659_0151490101_M2S00250IME.FIT ... OK
0659_0151490101_M2S00260IME.FIT ... OK
0659_0151490101_M2S00270IME.FIT ... OK
0659_0151490101_PNS00310IME.FIT ... not M1 M2
0659_0151490101_PNS00311IME.FIT ... not M1 M2
0659_0151490101_PNS00312IME.FIT ... not M1 M2
0659_0151490101_R1S00401SPE.FIT ... not M1 M2
0659_0151490101_R1S00402SPE.FIT ... not M1 M2
0659_0151490101_R1S00403SPE.FIT ... not M1 M2
0659_0151490101_R1S00404SPE.FIT ... not M1 M2
0659_0151490101_R1S00405SPE.FIT ... not M1 M2
0659_0151490101_R1S00406SPE.FIT ... not M1 M2
0659_0151490101_R1S00408SPE.FIT ... not M1 M2
 
 
 0: 0659_0151490101_M1S001
Instrument: M1  exposure: S001
CMD: rm -f *.in *.out merged.*
 
ccd: 1  node: 0
event0 : ../odf/0659_0151490101_M1S00110IME.FIT
 
CMD: emframes auxiliaryset=../odf/0659_0151490101_M1S00100AUX.FIT
frameset=frame01.out withodfeventset=Y
odfeventset=../odf/0659_0151490101_M1S00110IME.FIT neweventset=Y
outeventset=event01.in writegtiset=Y outgtiset=ccdgti01.in -w 10
emframes:- Executing (routine): emframes
auxiliaryset='../odf/0659_0151490101_M1S00100AUX.FIT' newframeset=yes
frameset='frame01.out' checkframes=yes withsrccoords=no srcra='0' srcdec='0'
flagbadtimes=no ingtiset='' flagfifooverflow=yes writegtiset=yes
outgtiset='ccdgti01.in' setgatti=yes withodfeventset=yes
odfeventset='../odf/0659_0151490101_M1S00110IME.FIT' checknvalid=yes
setdeadtime=yes cosmicsize=1.88 cosmicoutoverin=1 neweventset=yes
outeventset='event01.in'  -w 10 -V 1
emframes: OalServer.cc:709: class OalServer & operator <<(OalServer
&, vector<const Attributable *,allocator<const Attributable *>
>): Assertion `exp' failed.
 
emchain: That task ended in error !
 
frame01.out not created. Jump to next CCD.
 
ccd: 1  node: 1 : No data
 
ccd: 2  node: 0
event0 : ../odf/0659_0151490101_M1S00120IME.FIT
 
CMD: emframes auxiliaryset=../odf/0659_0151490101_M1S00100AUX.FIT
frameset=frame02.out withodfeventset=Y
odfeventset=../odf/0659_0151490101_M1S00120IME.FIT neweventset=Y
outeventset=event02.in writegtiset=Y outgtiset=ccdgti02.in -w 10
emframes:- Executing (routine): emframes
auxiliaryset='../odf/0659_0151490101_M1S00100AUX.FIT' newframeset=yes
frameset='frame02.out' checkframes=yes withsrccoords=no srcra='0' srcdec='0'
flagbadtimes=no ingtiset='' flagfifooverflow=yes writegtiset=yes
outgtiset='ccdgti02.in' setgatti=yes withodfeventset=yes
odfeventset='../odf/0659_0151490101_M1S00120IME.FIT' checknvalid=yes
setdeadtime=yes cosmicsize=1.88 cosmicoutoverin=1 neweventset=yes
outeventset='event02.in'  -w 10 -V 1
buote@neamh: ** emframes: error (copyDataSetFailed), It was not possible to copy
the dataset with name '../odf/0659_0151490101_M1S00120IME.FIT' to 'event02.in'


I killed it here.


Operating_System: RedHat 7.x

Other_Operating_System: 

Instrument: 

Data_Type: data products

Observation_Identifier: 0659_0151490101

Exposure_Identifier: 

Private: 

Submitted_From: 128.200.44.88 (128.200.44.88)

Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030131

Referer: http://xmm.vilspa.es

Message of length 5019 truncated

Reply 1

Resend
From: Rosario Gonzalez Riestra <xmmhelp@xmm.vilspa.esa.es>
To: buote@uci.edu
Subject: Re: emchain crashes on brand new data set (PR#9156)
Date: Tue Sep 16 08:32:17 2003

Dear Dr. Buote,

The error you report is most likely caused because the SAS_ODF environment
variable is not correctly set. It should point to the *SUM.SAS file created by
'odfingest' (not to the odf directory).

Please make this change and try again. 

In case it does not work, pleas send us the sas_log with verbosity 6.

Regards,

		Rosario Gonzalez-Riestra
		XMM-SOC User Support Group
	


Followup 1

Compose reply
Download message
Subject: Re: emchain crashes on brand new data set (PR#9156)
From: David Buote <buote@uci.edu>
To: Rosario Gonzalez Riestra <xmmhelp@xmm.vilspa.esa.es>
Date: 17 Sep 2003 11:30:15 -0700
Dear Rosario,

Thank you for your reply. In the past, I have always set SAS_ODF to the
odf directory and that has always worked -- and still works on all other
data sets except this new one. If I set SAS_ODF to the *SUM.SAS file
then the output from emchain at the beginning is:

Options passed to individual tasks:  -w 10 |
withbadpixfind = yes |
ODF directory = ../odf/../odf/

Usually, this is just "../odf". Howver, it does achieve the same thing. 


The PATH variable at the top of the *SUM.SAS file was:

../odf/../odf/../odf/

So I changed this to "../odf"


Interestingly, after first trying emchain this way I no longer received
the error message reported previously as you correctly predicted. So I
tried emchain again. This time it worked for a while. It seemed to make
a first pass through all the chips and did some merging. However, on the
second pass through the chips a new error occurred involving "attcalc" 


CMD: rm -f merged.* P0151490101M1S001MIEVLI0000.FIT
P0151490101M1S001FBKTSR0000.FIT P0151490101M1S001FBKGTI0000.FIT
CMD: rm -f event*.out
 
ccd: 1  node: 0
CMD: badpix eventset=event01.in withoutset=N windowfilter=Y
getnewbadpix=Y badpixset=badpix01.out getuplnkbadpix=Y getotherbadpix=N
-w 10
badpix:- Executing (routine): badpix eventset='event01.in'
getuplnkbadpix=yes getotherbadpix=no getnewbadpix=yes
badpixset='badpix01.out' emptyextension=no windowfilter=yes
withoutset=no outset='out.fits'  -w 10 -V 1
 
ccd: 1  node: 1 : No data
 
CMD: emevents odfeventset=event01.in eventset=event01.out withframeset=Y
frameset=frame01.out randomizetime=Y -w 10
emevents:- Executing (routine): emevents odfeventset='event01.in'
newoutput=yes eventset='event01.out' withframeset=yes
frameset='frame01.out' flagbadtimes=yes flagtruncatede1=yes
writegattispecset=no gattispecset='gattispec.out' withoffvarsets=no
offvarsets='' withothernode=no othereventset='' otherframeset=''
analysepatterns=yes flagbadpixels=yes splitdiagonals=yes keepsifluor=no
setcoordinates=yes randomizeposition=yes rejectrows=yes
maxeventsperrow=4 rejectbade3=yes e3thresholds='-29 -68 -40 -45 -34 -41
-51 -36 -57 -30 -23 -27 -36 -29' settimes=yes randomizetime=yes
blocksize=10000  -w 10 -V 1
CMD: cp ccdgti01.in gti01.out
CMD: attcalc eventset=event01.out -w 10
attcalc:- Executing (routine): attcalc eventset='event01.out'
attitudelabel='ahf' refpointlabel='pnt' withatthkset=yes
atthkset='atthk.dat' withmedianpnt=yes fixedra='0' fixeddec='0'
fixedposangle='0' imagesize='0.36' nominalra='0' nominaldec='0'  -w 10
-V 1
** attcalc: warning (creatorKeywordNotFound), The CREATOR keyword could
not be found in dataset with name 'atthk.dat'
** attcalc: warning (dateKeywordNotFound), The DATE keyword could not be
found in dataset with name 'atthk.dat'
** attcalc: warning (unnamedTable), A fits table was found without a
name.
** attcalc: error (attributableNotFound), Could not find attribute with
qualified name atthk.dat%MAHFRA in attributable set atthk.dat
 
emchain: That task ended in error !
 
CMD: emenergy ineventset=event01.out -w 10
emenergy:- Executing (routine): emenergy ineventset='event01.out'
newoutput=no outeventset='events.out' flagevents=yes correctcti=yes
getccdbkg=yes minenergy=100 maxperipix=0 fillccdbkg=yes fillminnumber=10
useccfdarkframe=no withmaskedccdset=no maskedccdset=''
writebackgroundset=no backgroundset='bkgccd.map' timebin=100
rejectbade3e4=yes e3e4ellipse='0.00577 -0.0355 1.25 0.74 -1.05'
makepha=yes randomizeenergy=yes correctgain=yes  -w 10 -V 1



Indeed, atthk.dat does not have the CREATOR keyword:


buote@nifol: fkeyprint atthk.dat CREATOR
  
# FILE: atthk.dat
# KEYNAME: CREATOR
  
# EXTENSION:    0
  
# EXTENSION:    1


This does not happen on any of my other datasets. Strange....

Thanks for any help,
David 





On Tue, 2003-09-16 at 01:32, Rosario Gonzalez Riestra wrote:
> Dear Dr. Buote,
> 
> The error you report is most likely caused because the SAS_ODF environment
> variable is not correctly set. It should point to the *SUM.SAS file created
by
> 'odfingest' (not to the odf directory).
> 
> Please make this change and try again. 
> 
> In case it does not work, pleas send us the sas_log with verbosity 6.
> 
> Regards,
> 
> 		Rosario Gonzalez-Riestra
> 		XMM-SOC User Support Group
> 	
-- 
David Buote <buote@uci.edu>



Reply 2

Resend
From: Rosario Gonzalez Riestra <xmmhelp@xmm.vilspa.esa.es>
To: buote@uci.edu
Subject: Re: emchain crashes on brand new data set (PR#9156)
Date: Thu Sep 18 10:34:51 2003
Dear David,

I am quite puzzled with this problem. I have processed your
observation twice through emchain and I did not get any error. The
only explanation would be that the atthk.dat was corrupted for some
reason.

I do not think that the missing 'CREATOR' or 'DATE' keywords are the
real problem, but the non-existing atthk.dat%MAHFRA.
(if the atthk.dat already exists it is not re-computed again by emchain)


I would suggest that you delete this file and run emchain again.
Please let me know it it works 

Regards,


                 Rosario


Followup 2

Compose reply
Download message
Subject: Re: emchain crashes on brand new data set (PR#9156)
From: David Buote <buote@uci.edu>
To: Rosario Gonzalez Riestra <xmmhelp@xmm.vilspa.esa.es>
Date: 18 Sep 2003 11:09:49 -0700
Dear Rosario,

Deleting "atthk.dat" did the trick! Very strange indeed.

Thanks again for your help,
David



On Thu, 2003-09-18 at 03:34, Rosario Gonzalez Riestra wrote:
> Dear David,
> 
> I am quite puzzled with this problem. I have processed your
> observation twice through emchain and I did not get any error. The
> only explanation would be that the atthk.dat was corrupted for some
> reason.
> 
> I do not think that the missing 'CREATOR' or 'DATE' keywords are the
> real problem, but the non-existing atthk.dat%MAHFRA.
> (if the atthk.dat already exists it is not re-computed again by emchain)
> 
> 
> I would suggest that you delete this file and run emchain again.
> Please let me know it it works 
> 
> Regards,
> 
> 
>                  Rosario
-- 
David Buote <buote@uci.edu>


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