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 EPICMOS/8814
Full headers

From: dasmith@xray.astro.umass.edu
Subject: EPIC MOS event files
Compose reply
Download message
Move To:
1 replies: 1
0 followups:

Private message: yes  no

Notes:

Notification:


Date: Mon, 14 Jul 2003 23:06:03 GMT
From: dasmith@xray.astro.umass.edu
To: xmmhelp@xmm.vilspa.esa.es
CC: dasmith@xray.astro.umass.edu
Subject: EPIC MOS event files
Full_Name: David Smith
Submission from: (NULL) (128.119.51.37)


Hi,

I'm analyzing data from obsid 0083250101.  The program "emchain" produces  four

event files for both MOS1 and MOS2.  The MOS1 event files are named 

 P0083250101M1S002MIEVLI0000.FIT
 P0083250101M1U002MIEVLI0000.FIT
 P0083250101M1U003MIEVLI0000.FIT
 P0083250101M1U004MIEVLI0000.FIT

What do the S and U stand for?  Also, is it possible to analyze these files 
simultaneously? 

Regards,
Dave Smith.


Reply 1

Resend
From: Rosario Gonzalez Riestra <xmmhelp@xmm.vilspa.esa.es>
To: dasmith@xray.astro.umass.edu
Subject: Re: EPIC MOS event files (PR#8814)
Date: Tue Jul 15 10:16:42 2003

Dear Dr. Smith,


The reason for having for different event files for MOS1 in your observation is
as follows:

There was initially only one scheduled exposure for MOS1. This is the file
labeled with S002 (S stands for Scheduled, U stands for Unscheduled).

This first observation was interrupted due to the high radiation level, and it
was re-started later (this is U002). 

The interruption happened two more times, therefore there are two further
exposures (U003 and U004).


Different EPIC event files can be merged with the SAS task 'merge', whose
description is at the following URL:

http://xmm.vilspa.esa.es/sas/current/doc/merge/index.html

Should you have any further question, please do not hesitate to contact us.

Regards,

				Rosario Gonzalez-Riestra
				XMM-SOC User Support Group

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