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 EPICpn/13
Full headers

From: loic.guennou@gmail.com
Subject: Error when launching XMM pipeline commands
Compose reply
Download message
Move To:
1 replies: 1
2 followups: 1 2

Private message: yes  no

Notes:

Notification:


Date: Thu, 22 Aug 2013 15:30:45 GMT
From: loic.guennou@gmail.com
To: xmmhelp@sciops.esa.int
Cc: loic.guennou@gmail.com
Subject: Error when launching XMM pipeline commands
Full_Name: loic guennou
Submission from: (NULL) (195.221.212.242)


I try to launch the commands epchain and emchain with the sas package. I obtain
the following message on my shell:

Options passed to individual tasks:  -w 10 |
ODF directory = /home/cadami/A209/odf/ 

List of files in working directory : 
0202_0084230301_PNS00312IME.FIT ... not M1 M2
0202_0084230301_M2S00220IME.FIT ... OK
0202_0084230301_R2S00501SPE.FIT ... not M1 M2
0202_0084230301_R1S00401SPE.FIT ... not M1 M2
0202_0084230301_PNS00301IME.FIT ... not M1 M2
0202_0084230301_PNS00302IME.FIT ... not M1 M2
0202_0084230301_PNS00303IME.FIT ... not M1 M2
0202_0084230301_M1S00130IME.FIT ... OK
0202_0084230301_R2S00502SPE.FIT ... not M1 M2
0202_0084230301_M2S00270IME.FIT ... OK
0202_0084230301_R2S00508SPE.FIT ... not M1 M2
0202_0084230301_PNS00311IME.FIT ... not M1 M2
0202_0084230301_M1S00170IME.FIT ... OK
0202_0084230301_R2S00505SPE.FIT ... not M1 M2
0202_0084230301_PNS00308IME.FIT ... not M1 M2
0202_0084230301_M2S00210IME.FIT ... OK
0202_0084230301_M1S00120IME.FIT ... OK
0202_0084230301_PNS00307IME.FIT ... not M1 M2
0202_0084230301_R1S00409SPE.FIT ... not M1 M2
0202_0084230301_M1S00110IME.FIT ... OK
0202_0084230301_M1S00150IME.FIT ... OK
0202_0084230301_R2S00507SPE.FIT ... not M1 M2
0202_0084230301_M2S00240IME.FIT ... OK
0202_0084230301_R2S00509SPE.FIT ... not M1 M2
0202_0084230301_R2S00506SPE.FIT ... not M1 M2
0202_0084230301_M2S00250IME.FIT ... OK
0202_0084230301_R1S00404SPE.FIT ... not M1 M2
0202_0084230301_PNS00304IME.FIT ... not M1 M2
0202_0084230301_M2S00260IME.FIT ... OK
0202_0084230301_R1S00405SPE.FIT ... not M1 M2
0202_0084230301_PNS00306IME.FIT ... not M1 M2
0202_0084230301_R1S00406SPE.FIT ... not M1 M2
0202_0084230301_R1S00402SPE.FIT ... not M1 M2
0202_0084230301_M2S00230IME.FIT ... OK
0202_0084230301_PNS00310IME.FIT ... not M1 M2
0202_0084230301_R2S00503SPE.FIT ... not M1 M2
0202_0084230301_PNS00305IME.FIT ... not M1 M2
0202_0084230301_M1S00140IME.FIT ... OK
0202_0084230301_PNS00309IME.FIT ... not M1 M2
0202_0084230301_R1S00408SPE.FIT ... not M1 M2
0202_0084230301_R1S00403SPE.FIT ... not M1 M2
0202_0084230301_M1S00160IME.FIT ... OK


 0: 0202_0084230301_M2S002
Instrument: M2  exposure: S002
CMD: rm -f *.in.mos *.out.mos merged.*.mos 

ccd: 1  node: 0
event0 : /home/cadami/A209/odf/0202_0084230301_M2S00210IME.FIT 

CMD: emframes auxiliaryset=/home/cadami/A209/odf/0202_0084230301_M2S00200AUX.FIT
frameset=frame01.out.mos
odfeventset=/home/cadami/A209/odf/0202_0084230301_M2S00210IME.FIT
outeventset=event01.in.mos outgtiset=ccdgti01.in.mos -w 10
AUX set name: /home/cadami/A209/odf//0202_0084230301_M2S00200AUX.FIT
fkeyprint: symbol lookup error:
/home/cadami/loic/heasoft-6.14/x86_64-unknown-linux-gnu-libc2.5/lib/libxanlib_6.14.so:
undefined symbol: _gfortran_copy_string
fkeyprint: symbol lookup error:
/home/cadami/loic/heasoft-6.14/x86_64-unknown-linux-gnu-libc2.5/lib/libxanlib_6.14.so:
undefined symbol: _gfortran_copy_string

emchain: warning(badstring) !
Non-standard INSTRUME =  |
INSTRUME set to _____

emchain: warning(badinstrument) !
INSTRUME = _____ in frame01.out.mos[0] is not EMOS
ccd: 1 node: 1 : No data 

I am sure to have all the necessary files and fit files fir it. Can you please
help me?
thank you


Followup 1

Compose reply
Download message
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: loic.guennou@gmail.com
Subject: Re: Error when launching XMM pipeline commands (PR#13)
Date: Fri Aug 23 07:36:27 2013
Dear Loic Guennou,

 I downloaded the data and ran epchain and emchain without problems. Please
describe what you have done so I can reproduce the error.

 This is what you need to do:
1) Download data, store and unpack in /home/cadami/A209/odf/ 
2) Run startup thread
   http://xmm.esac.esa.int/sas/current/documentation/threads/sas_startup_thread.shtml
    Thus: cifbuild
          set environment variable SAS_CCF to the full path of the ccf.cif file
          odfingest
          set environment variable SAS_ODF to the full path of the
0202_0084230301_SCX00000SUM.SAS file
3) Run epchain and emchain:
   emchain -V 5 >& emchain.log
   epchain -V 5 >& epchain.log

If this is what you have done, then please run the following commands:
   sasversion >& mysassetup.log
   uname -a >>& mysassetup.log
   env >>& mysassetup.log

and send us back the two files mysassetup.log and the log files from step 3
emchain.log and epchain.log

 Best regards,
Jan-Uwe

> 
> I try to launch the commands epchain and emchain with the sas package. I
obtain
> the following message on my shell:
> 
> Options passed to individual tasks:  -w 10 |
> ODF directory = /home/cadami/A209/odf/ 
> 
> List of files in working directory : 
> 0202_0084230301_PNS00312IME.FIT ... not M1 M2
> 0202_0084230301_M2S00220IME.FIT ... OK
> 0202_0084230301_R2S00501SPE.FIT ... not M1 M2
> 0202_0084230301_R1S00401SPE.FIT ... not M1 M2
> 0202_0084230301_PNS00301IME.FIT ... not M1 M2
> 0202_0084230301_PNS00302IME.FIT ... not M1 M2
> 0202_0084230301_PNS00303IME.FIT ... not M1 M2
> 0202_0084230301_M1S00130IME.FIT ... OK
> 0202_0084230301_R2S00502SPE.FIT ... not M1 M2
> 0202_0084230301_M2S00270IME.FIT ... OK
> 0202_0084230301_R2S00508SPE.FIT ... not M1 M2
> 0202_0084230301_PNS00311IME.FIT ... not M1 M2
> 0202_0084230301_M1S00170IME.FIT ... OK
> 0202_0084230301_R2S00505SPE.FIT ... not M1 M2
> 0202_0084230301_PNS00308IME.FIT ... not M1 M2
> 0202_0084230301_M2S00210IME.FIT ... OK
> 0202_0084230301_M1S00120IME.FIT ... OK
> 0202_0084230301_PNS00307IME.FIT ... not M1 M2
> 0202_0084230301_R1S00409SPE.FIT ... not M1 M2
> 0202_0084230301_M1S00110IME.FIT ... OK
> 0202_0084230301_M1S00150IME.FIT ... OK
> 0202_0084230301_R2S00507SPE.FIT ... not M1 M2
> 0202_0084230301_M2S00240IME.FIT ... OK
> 0202_0084230301_R2S00509SPE.FIT ... not M1 M2
> 0202_0084230301_R2S00506SPE.FIT ... not M1 M2
> 0202_0084230301_M2S00250IME.FIT ... OK
> 0202_0084230301_R1S00404SPE.FIT ... not M1 M2
> 0202_0084230301_PNS00304IME.FIT ... not M1 M2
> 0202_0084230301_M2S00260IME.FIT ... OK
> 0202_0084230301_R1S00405SPE.FIT ... not M1 M2
> 0202_0084230301_PNS00306IME.FIT ... not M1 M2
> 0202_0084230301_R1S00406SPE.FIT ... not M1 M2
> 0202_0084230301_R1S00402SPE.FIT ... not M1 M2
> 0202_0084230301_M2S00230IME.FIT ... OK
> 0202_0084230301_PNS00310IME.FIT ... not M1 M2
> 0202_0084230301_R2S00503SPE.FIT ... not M1 M2
> 0202_0084230301_PNS00305IME.FIT ... not M1 M2
> 0202_0084230301_M1S00140IME.FIT ... OK
> 0202_0084230301_PNS00309IME.FIT ... not M1 M2
> 0202_0084230301_R1S00408SPE.FIT ... not M1 M2
> 0202_0084230301_R1S00403SPE.FIT ... not M1 M2
> 0202_0084230301_M1S00160IME.FIT ... OK
> 
> 
>  0: 0202_0084230301_M2S002
> Instrument: M2  exposure: S002
> CMD: rm -f *.in.mos *.out.mos merged.*.mos 
> 
> ccd: 1  node: 0
> event0 : /home/cadami/A209/odf/0202_0084230301_M2S00210IME.FIT 
> 
> CMD: emframes auxiliaryset=/home/cadami/A209/odf/0202_0084230301_M2S00200AUX.FIT
> frameset=frame01.out.mos
> odfeventset=/home/cadami/A209/odf/0202_0084230301_M2S00210IME.FIT
> outeventset=event01.in.mos outgtiset=ccdgti01.in.mos -w 10
> AUX set name: /home/cadami/A209/odf//0202_0084230301_M2S00200AUX.FIT
> fkeyprint: symbol lookup error:
> /home/cadami/loic/heasoft-6.14/x86_64-unknown-linux-gnu-libc2.5/lib/libxanlib_6.14.so:
> undefined symbol: _gfortran_copy_string
> fkeyprint: symbol lookup error:
> /home/cadami/loic/heasoft-6.14/x86_64-unknown-linux-gnu-libc2.5/lib/libxanlib_6.14.so:
> undefined symbol: _gfortran_copy_string
> 
> emchain: warning(badstring) !
> Non-standard INSTRUME =  |
> INSTRUME set to _____
> 
> emchain: warning(badinstrument) !
> INSTRUME = _____ in frame01.out.mos[0] is not EMOS
> ccd: 1 node: 1 : No data 
> 
> I am sure to have all the necessary files and fit files fir it. Can you
please
> help me?
> thank you
> 
> 


Reply 1

Resend
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: loic.guennou@gmail.com
Subject: Re: Error when launching XMM pipeline commands (PR#13)
Date: Mon Sep 16 12:26:28 2013
Dear Loic Guennou,

 regarding your question from last month, we have not heard back from you any
more and hope this means that the problem is solved. I will now close this
ticket. You can still reply to this ticket or a open new ticket if you have
further questions.

 Best regards,
Jan-Uwe

Dr. Jan-Uwe Ness
XMM-Newton Science Operations Centre


Fri Aug 23 07:36:27 2013, xmmhelp wrote:
> Dear Loic Guennou,
> 
>  I downloaded the data and ran epchain and emchain without problems.
Please
> describe what you have done so I can reproduce the error.
> 
>  This is what you need to do:
> 1) Download data, store and unpack in /home/cadami/A209/odf/ 
> 2) Run startup thread
>    http://xmm.esac.esa.int/sas/current/documentation/threads/sas_startup_thread.shtml
>     Thus: cifbuild
>           set environment variable SAS_CCF to the full path of the ccf.cif
file
>           odfingest
>           set environment variable SAS_ODF to the full path of the
> 0202_0084230301_SCX00000SUM.SAS file
> 3) Run epchain and emchain:
>    emchain -V 5 >& emchain.log
>    epchain -V 5 >& epchain.log
> 
> If this is what you have done, then please run the following commands:
>    sasversion >& mysassetup.log
>    uname -a >>& mysassetup.log
>    env >>& mysassetup.log
> 
> and send us back the two files mysassetup.log and the log files from step
3
> emchain.log and epchain.log
> 
>  Best regards,
> Jan-Uwe
> 
>> 
>> I try to launch the commands epchain and emchain with the sas package.
>> I obtain the following message on my shell:
>> 
>> Options passed to individual tasks:  -w 10 |
>> ODF directory = /home/cadami/A209/odf/ 
>> 
>> List of files in working directory : 
>> 0202_0084230301_PNS00312IME.FIT ... not M1 M2
>> 0202_0084230301_M2S00220IME.FIT ... OK
>> 0202_0084230301_R2S00501SPE.FIT ... not M1 M2
>> 0202_0084230301_R1S00401SPE.FIT ... not M1 M2
>> 0202_0084230301_PNS00301IME.FIT ... not M1 M2
>> 0202_0084230301_PNS00302IME.FIT ... not M1 M2
>> 0202_0084230301_PNS00303IME.FIT ... not M1 M2
>> 0202_0084230301_M1S00130IME.FIT ... OK
>> 0202_0084230301_R2S00502SPE.FIT ... not M1 M2
>> 0202_0084230301_M2S00270IME.FIT ... OK
>> 0202_0084230301_R2S00508SPE.FIT ... not M1 M2
>> 0202_0084230301_PNS00311IME.FIT ... not M1 M2
>> 0202_0084230301_M1S00170IME.FIT ... OK
>> 0202_0084230301_R2S00505SPE.FIT ... not M1 M2
>> 0202_0084230301_PNS00308IME.FIT ... not M1 M2
>> 0202_0084230301_M2S00210IME.FIT ... OK
>> 0202_0084230301_M1S00120IME.FIT ... OK
>> 0202_0084230301_PNS00307IME.FIT ... not M1 M2
>> 0202_0084230301_R1S00409SPE.FIT ... not M1 M2
>> 0202_0084230301_M1S00110IME.FIT ... OK
>> 0202_0084230301_M1S00150IME.FIT ... OK
>> 0202_0084230301_R2S00507SPE.FIT ... not M1 M2
>> 0202_0084230301_M2S00240IME.FIT ... OK
>> 0202_0084230301_R2S00509SPE.FIT ... not M1 M2
>> 0202_0084230301_R2S00506SPE.FIT ... not M1 M2
>> 0202_0084230301_M2S00250IME.FIT ... OK
>> 0202_0084230301_R1S00404SPE.FIT ... not M1 M2
>> 0202_0084230301_PNS00304IME.FIT ... not M1 M2
>> 0202_0084230301_M2S00260IME.FIT ... OK
>> 0202_0084230301_R1S00405SPE.FIT ... not M1 M2
>> 0202_0084230301_PNS00306IME.FIT ... not M1 M2
>> 0202_0084230301_R1S00406SPE.FIT ... not M1 M2
>> 0202_0084230301_R1S00402SPE.FIT ... not M1 M2
>> 0202_0084230301_M2S00230IME.FIT ... OK
>> 0202_0084230301_PNS00310IME.FIT ... not M1 M2
>> 0202_0084230301_R2S00503SPE.FIT ... not M1 M2
>> 0202_0084230301_PNS00305IME.FIT ... not M1 M2
>> 0202_0084230301_M1S00140IME.FIT ... OK
>> 0202_0084230301_PNS00309IME.FIT ... not M1 M2
>> 0202_0084230301_R1S00408SPE.FIT ... not M1 M2
>> 0202_0084230301_R1S00403SPE.FIT ... not M1 M2
>> 0202_0084230301_M1S00160IME.FIT ... OK
>> 
>> 
>>  0: 0202_0084230301_M2S002
>> Instrument: M2  exposure: S002
>> CMD: rm -f *.in.mos *.out.mos merged.*.mos 
>> 
>> ccd: 1  node: 0
>> event0 : /home/cadami/A209/odf/0202_0084230301_M2S00210IME.FIT 
>> 
>> CMD: emframes
auxiliaryset=/home/cadami/A209/odf/0202_0084230301_M2S00200AUX.FIT
>> frameset=frame01.out.mos
>> odfeventset=/home/cadami/A209/odf/0202_0084230301_M2S00210IME.FIT
>> outeventset=event01.in.mos outgtiset=ccdgti01.in.mos -w 10
>> AUX set name: /home/cadami/A209/odf//0202_0084230301_M2S00200AUX.FIT
>> fkeyprint: symbol lookup error:
>> /home/cadami/loic/heasoft-6.14/x86_64-unknown-linux-gnu-libc2.5/lib/libxanlib_6.14.so:
>> undefined symbol: _gfortran_copy_string
>> fkeyprint: symbol lookup 

Message of length 5586 truncated


Followup 2

Compose reply
Download message
Date: Mon, 16 Sep 2013 14:29:05 +0200
From: Loic Guennou <loic.guennou@gmail.com>
To: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
Subject: Re: Error when launching XMM pipeline commands (PR#13)
This is a multi-part message in MIME format.
--------------000400020102090405090400
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

i am sorry to answer you this late. Things got a little hectic with a 
crash of pc and I completely forgot to send you a reply. We managed to 
make it work with the help of someone versed in programming on a new 
computer. In any case, thank you for your quick answer.

I wish you a good day
Lo.c Guennou

On 16/09/2013 14:26, Jan-Uwe Ness wrote:
> Dear Loic Guennou,
>
>   regarding your question from last month, we have not heard back from you
any
> more and hope this means that the problem is solved. I will now close this
> ticket. You can still reply to this ticket or a open new ticket if you have
> further questions.
>
>   Best regards,
> Jan-Uwe
>
> Dr. Jan-Uwe Ness
> XMM-Newton Science Operations Centre
>
>
> Fri Aug 23 07:36:27 2013, xmmhelp wrote:
>    
>> Dear Loic Guennou,
>>
>>   I downloaded the data and ran epchain and emchain without problems.
Please
>> describe what you have done so I can reproduce the error.
>>
>>   This is what you need to do:
>> 1) Download data, store and unpack in /home/cadami/A209/odf/
>> 2) Run startup thread
>>     http://xmm.esac.esa.int/sas/current/documentation/threads/sas_startup_thread.shtml
>>      Thus: cifbuild
>>            set environment variable SAS_CCF to the full path of the
ccf.cif
>>      
> file
>    
>>            odfingest
>>            set environment variable SAS_ODF to the full path of the
>> 0202_0084230301_SCX00000SUM.SAS file
>> 3) Run epchain and emchain:
>>     emchain -V 5>&  emchain.log
>>     epchain -V 5>&  epchain.log
>>
>> If this is what you have done, then please run the following commands:
>>     sasversion>&  mysassetup.log
>>     uname -a>>&  mysassetup.log
>>     env>>&  mysassetup.log
>>
>> and send us back the two files mysassetup.log and the log files from
step 3
>> emchain.log and epchain.log
>>
>>   Best regards,
>> Jan-Uwe
>>
>>      
>>> I try to launch the commands epchain and emchain with the sas
package.
>>> I obtain the following message on my shell:
>>>
>>> Options passed to individual tasks:  -w 10 |
>>> ODF directory = /home/cadami/A209/odf/
>>>
>>> List of files in working directory :
>>> 0202_0084230301_PNS00312IME.FIT ... not M1 M2
>>> 0202_0084230301_M2S00220IME.FIT ... OK
>>> 0202_0084230301_R2S00501SPE.FIT ... not M1 M2
>>> 0202_0084230301_R1S00401SPE.FIT ... not M1 M2
>>> 0202_0084230301_PNS00301IME.FIT ... not M1 M2
>>> 0202_0084230301_PNS00302IME.FIT ... not M1 M2
>>> 0202_0084230301_PNS00303IME.FIT ... not M1 M2
>>> 0202_0084230301_M1S00130IME.FIT ... OK
>>> 0202_0084230301_R2S00502SPE.FIT ... not M1 M2
>>> 0202_0084230301_M2S00270IME.FIT ... OK
>>> 0202_0084230301_R2S00508SPE.FIT ... not M1 M2
>>> 0202_0084230301_PNS00311IME.FIT ... not M1 M2
>>> 0202_0084230301_M1S00170IME.FIT ... OK
>>> 0202_0084230301_R2S00505SPE.FIT ... not M1 M2
>>> 0202_0084230301_PNS00308IME.FIT ... not M1 M2
>>> 0202_0084230301_M2S00210IME.FIT ... OK
>>> 0202_0084230301_M1S00120IME.FIT ... OK
>>> 0202_0084230301_PNS00307IME.FIT ... not M1 M2
>>> 0202_0084230301_R1S00409SPE.FIT ... not M1 M2
>>> 0202_0084230301_M1S00110IME.FIT ... OK
>>> 0202_0084230301_M1S00150IME.FIT ... OK
>>> 0202_0084230301_R2S00507SPE.FIT ... not M1 M2
>>> 0202_0084230301_M2S00240IME.FIT ... OK
>>> 0202_0084230301_R2S00509SPE.FIT ... not M1 M2
>>> 0202_0084230301_R2S00506SPE.FIT ... not M1 M2
>>> 0202_0084230301_M2S00250IME.FIT ... OK
>>> 0202_0084230301_R1S00404SPE.FIT ... not M1 M2
>>> 0202_0084230301_PNS00304IME.FIT ... not M1 M2
>>> 0202_0084230301_M2S00260IME.FIT ... OK
>>> 0202_0084230301_R1S00405SPE.FIT ... not M1 M2
>>> 0202_0084230301_PNS00306IME.FIT ... not M1 M2
>>> 0202_0084230301_R1S00406SPE.FIT ... not M1 M2
>>> 0202_0084230301_R1S00402SPE.FIT ... not M1 M2
>>> 0202_0084230301_M2S00230IME.FIT ... OK
>>> 0202_0084230301_PNS00310IME.FIT ... not M1 M2
>>> 0202_0084230301_R2S00503SPE.FIT ... not M1 M2
>>> 0202_0084230301_PNS00305IME.FIT ... not M1 M2
>>> 0202_0084230301_M1S00140IME.FIT ... OK
>>> 0202_0084230301_PNS00309IME.FIT ... not M1 M2
>>> 0202_0084230301_R1S00408SPE.FIT ... not M1 M2
>>> 0202_0084230301_R1S00403SPE.FIT ... not M1 M2
>>> 0202_0084230301_M1S00160IM

Message of length 13661 truncated

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