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 Backgrounds/15190
Full headers

From: jaturong sukonthachat <jaturong.sukonthachat@uibk.ac.at>
Subject: Calclosed-observation
Compose reply
Download message
Move To:
1 replies: 1
0 followups:

Private message: yes  no

Notes:

Notification:


Date: Thu, 24 Jun 2004 12:35:42 +0200
From: jaturong sukonthachat <jaturong.sukonthachat@uibk.ac.at>
Subject: Calclosed-observation
To: Matthias Ehle <xmmhelp@xmm.vilspa.esa.es>
This is a multi-part message in MIME format.
--------------020905080700020903000409
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Matthias,

There are 2 observations of my cluster, A3558, one is taken with a thick 
filter and another one is taken with  a calclosed filter. I want to 
estimate an background intrument component, e.g.  fluorescence lines by  
using  the observation that was taken with a calclosed filter. After I 
used an emproc task to make an events file of the calclosed-observation 
and appying a gti-correction, using the same value as I used for a 
thick-observation. I found that an average count rate of the 
thick-events is about 7.5 counts/sec but an average count rate of the 
calclosed-events is 45 counts/sec. This is imposible because a noise + 
fluorescence lines count rate is much higher than a observed X-ray count 
rate. (you can see in 2 histrgrams that was attached with this letter, 
both of them use time-bin-size = 100 sec.)

So that, I think I should do something wrong but I don't know that. 
There are a few questions that I want to ask you about this :

1. Can the emproc (epproc) use to make an events file from a calclosed 
observation ?

2. Is a unit of observation count rate and calclosed count rate the same ?

3. Do you know a document that explain a properties of a calclosed data ?

Thank you. :)

Cheers,
Loy. :)



--------------020905080700020903000409
Content-Type: application/postscript;
 name="his_m1_closed_f0_gti15_05to10.ps"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="his_m1_closed_f0_gti15_05to10.ps"

%!PS-Adobe-3.0
%%BoundingBox: 0 0 612 792
%%LanguageLevel: 2
%%Creator: Grace-5.1.14
%%CreationDate: Thu Jun 24 11:40:42 2004
%%DocumentData: Clean8Bit
%%Orientation: Landscape
%%Pages: 1
%%PageOrder: Ascend
%%Title: /tmp/dsplhCXdAI
%%For: jaturong
%%DocumentNeededResources: (atend)
%%EndComments
%%BeginProlog
/PAGE_OFFSET_X 0 def
/PAGE_OFFSET_Y 0 def
/m {moveto} def
/l {lineto} def
/s {stroke} def
/n {newpath} def
/c {closepath} def
/RL {rlineto} def
/SLW {setlinewidth} def
/GS {gsave} def
/GR {grestore} def
/SC {setcolor} def
/SGRY {setgray} def
/SRGB {setrgbcolor} def
/SD {setdash} def
/SLC {setlinecap} def
/SLJ {setlinejoin} def
/SCS {setcolorspace} def
/FFSF {findfont setfont} def
/CC {concat} def
/PXL {n m 0 0 RL s} def
/Color0 {1.0000 1.0000 1.0000} def
/Color1 {0.0000 0.0000 0.0000} def
/Color2 {1.0000 0.0000 0.0000} def
/Color3 {0.0000 1.0000 0.0000} def
/Color4 {0.0000 0.0000 1.0000} def
/Color5 {1.0000 1.0000 0.0000} def
/Color6 {0.7373 0.5608 0.5608} def
/Color7 {0.8627 0.8627 0.8627} def
/Color8 {0.5804 0.0000 0.8275} def
/Color9 {0.0000 1.0000 1.0000} def
/Color10 {1.0000 0.0000 1.0000} def
/Color11 {1.0000 0.6471 0.0000} def
/Color12 {0.4471 0.1294 0.7373} def
/Color13 {0.4039 0.0275 0.2824} def
/Color14 {0.2510 0.8784 0.8157} def
/Color15 {0.0000 0.5451 0.0000} def
/Color16 {0.7529 0.7529 0.7529} def
/Color17 {0.5059 0.5059 0.5059} def
/Color18 {0.2588 0.2588 0.2588} def
/PTRN {
 /pat_bits exch def 
 <<
  /PaintType 2
  /PatternType 1 /TilingType 1
  /BBox[0 0 16 16]
  /XStep 16 /YStep 16
  /PaintProc {
   pop
   16 16 true [-1 0 0 -1 16 16] pat_bits imagemask
  }
 >>
 [0.0016 0 0 0.0016 0 0]
 makepattern
} def
/Pattern0 {<0000000000000000000000000000000000000000000000000000000000000000>
PTRN} bind def
/Pattern1 {<ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff>
PTRN} bind def
/Pattern2 {<eeeeffffbbbbffffeeeeffffbbbbffffeeeeffffbbbbffffeeeeffffbbbbffff>
PTRN} bind def
/Pattern3 {<eeeebbbbeeeebbbbeeeebbbbeeeebbbbeeeebbbbeeeebbbbeeeebbbbeeeebbbb>
PTRN} bind def
/Pattern4 {<5555aaaa5555aaaa5555aaaa5555aaaa5555aaaa5555aaaa5555aaaa5555aaaa>
PTRN} bind def
/Pattern5 {<1111444411114444111144441111444411114444111144441111444411114444>
PTRN} bind def
/Pattern6 {<1111000044440000111100004444000011110000444400001111000044440000>
PTRN} bind def
/Pattern7 {<1010000000000000010100000000000010100000000000000101000000000000>
PTRN} bind def
/Pattern8 {<0000000000000000000000000000000000000000000000000000000000000000>
PTRN} bind def
/Pattern9 {<1e1e0f0f8787c3c3e1e1f0f078783c3c1e1e0f0f8787c3c3e1e1f0f078783c3c>
PTRN} bind def
/Pattern10 {<7878f0f0e1e1c3c387870f0f1e1e3c3c7878f0f0e1e1c3c387870f0f1e1e3c3c>
PTRN} bind def
/Pattern11 {<3333333333333333333333333333333333333333333333333333333333333333>
PTRN} bind def
/Pattern12 {<ffffffff00000000ffffffff00000000ffffffff00000000ffffffff00000000>
PTRN} bind def
/Pattern13 {<8181424224241818181824244242818181814242242418181818242442428181>
PTRN} bind def
/Pattern14 {<8080404020201010080804040202010180804040202010100808040402020101>
PTRN} bind def
/Pattern15 {<0101020204040808101020204040808001010202040408081010202040408080>
PTRN} bind def
/Pattern16 {<2222222222222222222222222222222222222222222222222222222222222222>
PTRN} bind de

Message of length 35292 truncated

Reply 1

Resend
From: Michel G. Breitfellner <xmmhelp@xmm.vilspa.esa.es>
To: jaturong.sukonthachat@uibk.ac.at
Subject: Re: Calclosed-observation (PR#15190)
Date: Mon Jun 28 10:36:56 2004
Dear Dr. Sukonthachat,

You should not use calclosed observations for background
determination of any kind. These, are for internal calibration
and engineering use only.

However, since calclosed observations are "normal" XMM
observations, at least concerning the data format, you
can of course
1. use emproc (epproc) to make event files
2. the units are the same as "normal science" observations
3. there is no special documentation about properties of
   calclosed data.

With best regards,
Michel G. Breitfellner
XMM-Newton 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