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 SAS_Hardware/21538
Full headers

From: jonmm@umich.edu
Subject: memory error
Compose reply
Download message
Move To:
2 replies: 1 2
0 followups:

Private message: yes  no

Notes:

Notification:


Date: Tue, 02 May 2006 08:49:12 -0400
From: jonmm@umich.edu
Subject: memory error
To: xmmhelp@xmm.vilspa.esa.es
Hello,

I am trying to run pipeline processing on my new observation of GRS 
1915+105, obsid 0401630201.

Whether running epproc or epchain, I get a memory error, saying that 
the task has tried to allocate too much memory.   The failure usually 
occurs in evselect or epframes.  I have attempted this on a number of 
different machines, some with very large memory and swap space, both on 
linux and on mac, and the result is always the same.  This result is 
not changed if I run sas using the "low" memory model.

I do not think that there is actually a memory problem, though I am not 
sure.  I have some concerns that the large offset pointing (RAWY = 30 
instead of 190, for this EPIC-pn timing mode observation) may be 
causing some difficulties.

I would like to request that XMM try to produce pipeline products for 
this observation on an accelerated schedule.  I fear that it may be a 
very long process indeed.  I will understand if this is not possible, 
but it would be very helpful  and most appreciated if it is possible.

Best regards,

Jon Miller





Reply 1

Resend
From: Michel G. Breitfellner <xmmhelp@xmm.vilspa.esa.es>
To: jonmm@umich.edu
Subject: Re: memory error (PR#21538)
Date: Wed May  3 13:57:56 2006
Dear Dr. Miller,

We are currently investigating the phenomenon you reported
and will come back to you as soon as possible.

With best regards,
Michel G. Breitfellner
XMM-Newton User Support Group


Reply 2

Resend
From: Michel G. Breitfellner <xmmhelp@sciops.esa.int>
To: jonmm@umich.edu
Subject: Re: memory error (PR#21538)
Date: Wed Oct  4 07:49:00 2006
Dear Dr. Miller,

The problem was indeed limited machine memory.
We managed to reduce the data without any trouble on 4GB RAM machine.
and produced the following products:

standard epproc output:
   1160_0401630201_AttHk.ds
   1160_0401630201_EPN_U002_04_Badpixels.ds
   1160_0401630201_EPN_U002_TimingEvts.ds
   1160_0401630201_SCX00000SUM.SAS

Some more specific products:
Rates for filtering using events with PI > 10000 eV:
   HErates.ds

Filtered event list with tabgtigen criterion of at most 6 counts/sec
in former rate file:
   PN_6cs_filtered.ds

Filtered event list eliminating just the first 10ksec:
   PN_filtered.ds

Image from filtered event list:
   PN_semifilt_image.ds

GTI produced by tabgtigen:
   gti_6cs.ds

The log of the processing of the data.
It should be noted that the SAS gives a warning on a time jump which may
affect timing analysis. The rest of the output log is nominal:
   sas_log

How can we pass these products to you? Do you have an anonymous ftp area
where we can deposit the tar file of 808 MB?

With best regards,
Michel G. Breitfellner
XMM-Newton User Support Group

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