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

From: mas@star.le.ac.uk
Subject: eexpmap reads neither coordinates nor GTI
Compose reply
Download message
Move To:
5 replies: 1 2 3 4 5
4 followups: 1 2 3 4

Private message: yes  no

Notes:

Notification:


Date: Thu, 22 Jan 2004 15:23:02 GMT
From: mas@star.le.ac.uk
To: xmmhelp@xmm.vilspa.esa.es
Subject: eexpmap reads neither coordinates nor GTI
Name: Masaaki Sakano

Email_Address: mas@star.le.ac.uk

Topic: tasks

Other_Topic: 

Usage_Mode: command line

SAS_Release: xmmsas_20030110_1802 - aka 5.4.1

Task_Version: eexpmap (eexpmap-3.27.2) [xmmsas_20030110_1802-5.4.1]

Type: report a bug

Title: eexpmap reads neither coordinates nor GTI

Description: I have made an event file, which has different reference
coordinates for X/Y from the nominal one (using attcalc) and a shorter GTI than
the nominal one. Then I have created the image from the event file, making sure
writedss=true is set.  Now I have tried to create a corresponding exposure map
using eexpmap as follows;
eexpmap imageset=im.fits attitudeset=a.ds eventset=a.evt expimageset=a_exp.fits
usedss=yes

However the created exposure map seems identical as the nominal one; i.e.,
neither the coordinates nor the GTI seem to be taken into account.

I am ataching the log file.

Regards,
Masa


% eexpmap -V 5 imageset=try_im.fits attitudeset='0406_0111350101_AttHk.ds'
eventset=try_m2.evt expimageset='try_exp.fits' usedss=yes
eexpmap:- Executing (routine): eexpmap imageset='try_im.fits'
attitudeset='0406_0111350101_AttHk.ds' eventset='try_m2.evt'
expimageset='"try_exp.fits"' withdetcoords=no withpatterns=yes pattern=' '
usedss=yes withvignetting=yes usefastpixelization=yes useoffset=no hducut=0
badclean=0 attrebin=4 pimin='2000' pimax='4500'  -V 5^M
eexpmap:- eexpmap (eexpmap-3.27.2)  [xmmsas_20030110_1802-5.4.1] started: 
2004-01-22T15:13:55.000^M
eexpmap:-  Datamode: IMAGING^M
eexpmap:-  Number of Grades:  0^M
eexpmap:-  Grades:^M
eexpmap:-  No grade selection. QE will be set to 1.^M
** eexpmap: warning (NullValues), NULL values in the attitude table were
ignored^M
** eexpmap: warning (NullValues), NULL values in the attitude table were
ignored^M
** eexpmap: warning (NullValues), NULL values in the attitude table were
ignored^M
** eexpmap: warning (NullValues), NULL values in the attitude table were
ignored^M
** eexpmap: warning (NullValues), NULL values in the attitude table were
ignored^M
** eexpmap: warning (NullValues), NULL values in the attitude table were
ignored^M
** eexpmap: warning (NullValues), NULL values in the attitude table were
ignored^M
** eexpmap: warning (NullValues), NULL values in the attitude table were
ignored^M
** eexpmap: warning (NullValues), NULL values in the attitude table were
ignored^M
** eexpmap: warning (NullValues), NULL values in the attitude table were
ignored^M
** eexpmap: warning (NullValues), NULL values in the attitude table were
ignored^M
eexpmap:-  1  extension XX: N points is 20046^M
eexpmap:-  2  extension XX: N points is 20033^M
eexpmap:-  3  extension XX: N points is 20023^M
eexpmap:-  4  extension XX: N points is 20029^M
eexpmap:-  5  extension XX: N points is 20029^M
eexpmap:-  6  extension XX: N points is 20023^M
eexpmap:-  7  extension XX: N points is 20029^M
eexpmap:-  number of att-histogram bins  16^M
eexpmap:- CCF constituents accessed by the calibration server:
CifEntry{EPN, LINCOORD, 9, /data/06/sas-ccf/EPN_LINCOORD_0009.CCF,
1998-01-01T00:00:00.000}
CifEntry{RGS2, LINCOORD, 8, /data/06/sas-ccf/RGS2_LINCOORD_0008.CCF,
1998-01-01T00:00:00.000}
CifEntry{XMM, BORESIGHT, 16, /data/06/sas-ccf/XMM_BORESIGHT_0016.CCF,
2000-01-01T00:00:00.000}
CifEntry{XMM, MISCDATA, 16, /data/06/sas-ccf/XMM_MISCDATA_0016.CCF,
1999-01-01T00:00:00.000}
CifEntry{XRT2, XAREAEF, 9, /data/06/sas-ccf/XRT2_XAREAEF_0009.CCF,
2000-01-13T00:00:00.000}

^M
eexpmap:-  doing EMOS2                ccd chip # 1^M
eexpmap:-  doing EMOS2                ccd chip # 2^M
eexpmap:-  doing EMOS2                ccd chip # 3^M
eexpmap:-  doing EMOS2                ccd chip # 4^M
eexpmap:-  doing EMOS2                ccd chip # 5^M
eexpmap:-  doing EMOS2                ccd chip # 6^M
eexpmap:-  doing EMOS2                ccd chip # 7^M
eexpmap:- eexpmap (eexpmap-3.27.2)  [xmmsas_20030110_1802-5.4.1] ended:   
2004-01-22T15:14:29.000^M
eexpmap:- eexpmap (eexpmap-3.27.2)  [xmmsas_20030110_1802-5.4.1] CPU time:
33.61s^M
eexpmap:- List of CCF constituents accessed during this run:
CifEntry{EMOS2, FILTERTRANSX, 11, /data/06/sas-ccf/EMOS2_FILTERTRANSX_0011.CCF,
1998-01-01T00:00:00.000}
CifEntry{EMOS2, LINCOORD, 16, /data/06/sas-ccf/EMOS2_LINCOORD_0016.CCF,
1998-01-01T00:00:00.000}
CifEntry{EPN, LINCOORD, 9, /data/06/sas-ccf/EPN_LINCOORD_0009.CCF,
1998-01-01T00:00:00.000}
CifEntry{RGS2, LINCOORD, 8, /data/06/sas-ccf/RGS2_LINCOORD_0008.CCF,
1998-01-01T00:00:00.000}
CifEntry{RGS2, LINESPREADFUNC, 4, /data/06/sas-ccf/RGS2_LINESPREADFUNC_0004.CCF,
1999-01-01T00:00:00.000}
CifEntry{RGS2, QUANTUMEF, 9, /data/06/sas-ccf/RGS2_QUANTUMEF_0009.CCF,
1998-01-01T00:00:00.000}
CifEntry{XMM, BORESIGHT, 16, /data/06/sas-ccf/XMM_BORESIGHT_0016.CCF,
2000-01-01T00:00:00.000}
CifEntry{XMM, MISCDATA, 16, /data/06/sas-ccf/XMM_MISCDATA_0016.CCF,
1999-01-01T00:00:00.000}
CifEntry{XRT2, XAREAEF, 9, /data/06/sas-ccf/XRT2_XAREAEF_0009.CCF,
2000-01-13T00:00:00.000}

% 
% fstruct try_im.fits
  No. Type     EXTNAME      BITPIX Dimensio

Message of length 7298 truncated

Reply 1

Resend
From: Nora Loiseau <xmmhelp@xmm.vilspa.esa.es>
To: mas@star.le.ac.uk
Subject: Re: eexpmap reads neither coordinates nor GTI (PR#9955)
Date: Fri Jan 23 17:59:46 2004
Dear Dr. Sakano,

we are investigating your problem and will come back to you as soon as we have
an answer.

Best regards,

Nora
----
Dr. Nora Loiseau
XMM-Newton User Support Group


Followup 1

Compose reply
Download message
Date: Wed, 11 Feb 2004 12:51:12 +0000
From: Masaaki Sakano <mas@star.le.ac.uk>
To: Nora Loiseau <xmmhelp@xmm.vilspa.esa.es>
Subject: Re: eexpmap reads neither coordinates nor GTI (PR#9955)
Dear Nora,

Have you found anything on this problem?
# More than two weeks have passed since I submitted this.

Best regards,
Masa



Reply 2

Resend
From: Nora Loiseau <xmmhelp@xmm.vilspa.esa.es>
To: mas@star.le.ac.uk
Subject: Re: eexpmap reads neither coordinates nor GTI (PR#9955)
Date: Wed Feb 11 15:53:30 2004
Dear Masa,

we are very sorry for the delay. We here can not see any problem in the way 
you applied eexmap, we are trying to contact the developer of this task as it 
seems to be a real bug, but he will not be available until next week. In the 
mean time, for gaining time when he investigates the problem, could you put 
the files that you are using in a public directory at your place, so we can 
ftp them ?
We would need the original and modified attitude files, new GTI, event file, 
etc.

Best regards,

Nora


Followup 2

Compose reply
Download message
Date: Wed, 11 Feb 2004 16:40:36 +0000
From: Masaaki Sakano <mas@star.le.ac.uk>
To: Nora Loiseau <xmmhelp@xmm.vilspa.esa.es>
Subject: Re: eexpmap reads neither coordinates nor GTI (PR#9955)
Dear Nora,

You can find the related files below
	ftp://ftp.star.le.ac.uk/pub/mas/xmm/
		0406_0111350101_AttHk.ds
		0406_0111350101_EMOS2_S005_ImagingEvts.ds
		try_m2.evt
		try_im.fits
		try_exp.fits

1) Attitude file (0406_0111350101_AttHk.ds): The nominal one

2) Event files: 0406_0111350101_EMOS2_S005_ImagingEvts.ds  try_m2.evt
	0406_0111350101_EMOS2_S005_ImagingEvts.ds is made by
		emproc filterexpression='TIME<131089000'
	try_m2.evt is then further modified by
		cp 0406_0111350101_EMOS2_S005_ImagingEvts.ds try_m2.evt
		attcalc eventset=try_m2.evt refpointlabel=user nominalra=266.6123
nominaldec=-28.7582222222222 withatthkset=yes atthkset=0406_0111350101_AttHk.ds

3) Image file: try_im.fits   (created from the modified event file: try_m2.evt)
	made by
		evselect table=try_m2.evt withfilteredset=true xcolumn='X' ycolumn='Y'
ximagebinsize=80 yimagebinsize=80 imagebinning='binSize' imageset=try_im.fits
withimageset=true writedss=true

4) Resultant exposure map: try_exp.fits
	see my first mail for detail.


The GTI information is included in both the event and image FITS-files.

I hope this information is helpful.

Best regards,
Masa



Reply 3

Resend
From: Nora Loiseau <xmmhelp@xmm.vilspa.esa.es>
To: mas@star.le.ac.uk
Subject: Re: eexpmap reads neither coordinates nor GTI (PR#9955)
Date: Wed Feb 11 16:54:45 2004
Dear Masa,

thank you for the information, I hope we can come soon with a solution.

Best regards,

Nora


Followup 3

Compose reply
Download message
Date: Mon, 05 Apr 2004 20:38:41 +0100
From: Masaaki Sakano <mas@star.le.ac.uk>
To: Nora Loiseau <xmmhelp@xmm.vilspa.esa.es>
Subject: Re: eexpmap reads neither coordinates nor GTI (PR#9955)
Dear Nora,

Have you found anything on this problem?

I have tried the newly-release SAS [xmmsas_20040318_1831-6.0.0]
on this problem; however the problem still remains.

In SAS6 the new task, attmove, is introduced.  I had a look at the task,
and found it not to be applicable in this case, probably.
I guess that if it is ever possible to create two attitude files as well as
two ODF sets for the formar and latter-half periods in the observation,
which have different attitudes, and if one can treat them as the
completely separate data, all the problem will be easily solved.

Anyway I am looking forward to hearing from you.

Best regards,
Masa



Reply 4

Resend
From: Nora Loiseau <xmmhelp@xmm.vilspa.esa.es>
To: mas@star.le.ac.uk
Subject: Re: eexpmap reads neither coordinates nor GTI (PR#9955)
Date: Tue Apr 13 14:47:06 2004
Dear Masa,

our expert is back from a sick leave and was trying to have a look at your
problem, but he did not find the files, maybe they were deleted in
the meantime. Could you please put them in this place again?
I would the ask him to look also at your suggestion of splitting the
data for the two different attitudes.

Best regards,

Nora
 
> You can find the related files below
> 	ftp://ftp.star.le.ac.uk/pub/mas/xmm/
> 		0406_0111350101_AttHk.ds
> 		0406_0111350101_EMOS2_S005_ImagingEvts.ds
> 		try_m2.evt
> 		try_im.fits
> 		try_exp.fits
> 
> 1) Attitude file (0406_0111350101_AttHk.ds): The nominal one
> 
> 2) Event files: 0406_0111350101_EMOS2_S005_ImagingEvts.ds  try_m2.evt
> 	0406_0111350101_EMOS2_S005_ImagingEvts.ds is made by
> 		emproc filterexpression='TIME<131089000'
> 	try_m2.evt is then further modified by
> 		cp 0406_0111350101_EMOS2_S005_ImagingEvts.ds try_m2.evt
> 		attcalc eventset=try_m2.evt refpointlabel=user nominalra=266.6123
> nominaldec=-28.7582222222222 withatthkset=yes
atthkset=0406_0111350101_AttHk.ds
> 
> 3) Image file: try_im.fits   (created from the modified event file:
try_m2.evt)
> 	made by
> 		evselect table=try_m2.evt withfilteredset=true xcolumn='X' ycolumn='Y'
> ximagebinsize=80 yimagebinsize=80 imagebinning='binSize'
imageset=try_im.fits
> withimageset=true writedss=true
> 
> 4) Resultant exposure map: try_exp.fits
> 	see my first mail for detail.
> 
> 
> The GTI information is included in both the event and image FITS-files.
> 
> I hope this information is helpful.
> 
> Best regards,
> Masa
> 
> ----
Dr. Nora Loiseau
XMM-Newton User Support Group


Followup 4

Compose reply
Download message
Date: Wed, 14 Apr 2004 19:06:40 +0100
From: Masaaki Sakano <mas@star.le.ac.uk>
To: Nora Loiseau <xmmhelp@xmm.vilspa.esa.es>
Subject: Re: eexpmap reads neither coordinates nor GTI (PR#9955)
Dear Nora,

Thank you for your reply.

At Tue, 13 Apr 2004 14:47:05 GMT,
Nora Loiseau wrote:
> our expert is back from a sick leave and was trying to have a look at your
> problem, but he did not find the files, maybe they were deleted in
> the meantime. Could you please put them in this place again?

I have put the files again on the anonymous FTP site.

I am looking forward to hearing a good news from you.

Best regards,
Masa


> > You can find the related files below
> > 	ftp://ftp.star.le.ac.uk/pub/mas/xmm/
> > 		0406_0111350101_AttHk.ds
> > 		0406_0111350101_EMOS2_S005_ImagingEvts.ds
> > 		try_m2.evt
> > 		try_im.fits
> > 		try_exp.fits
> > 



Reply 5

Resend
From: Nora Loiseau <xmmhelp@xmm.vilspa.esa.es>
To: mas@star.le.ac.uk
Subject: Re: eexpmap reads neither coordinates nor GTI (PR#9955)
Date: Tue Jun 15 15:30:50 2004
Dear Masa,

please find below the reply of an EPIC expert about this problem.

I am sending the tar file he sent us in a separate mail.

Best regards,

Nora

---------

We have investiagted a problem mentioned in your e-mail regarding
task eexpmap and found that eexpmap correctly uses both information;
ie. coordinates and GTI.

The matter is that, eexpmap as a TIME filtering information uses
GTIs present as a dss blocks in an image input datasets.
Meanwhile, in a user's problem events list file created by:

emproc filterexpression='TIME<131089000'

does not create dss blocks of STDGTIs according used filterexpression
(check image's STDGTIs).

Instead can be used a command tabgtigen (as you may see from attached
shell script used by me for creation images and expmaps for this specific
case).

So, an attached tar gziped file contains 4 expmap images and a shell
script which has been used to create these images.
As a starting point for us served pipeline products of that observation
(Obs. ID 0111350101,  MOS 2) and results showed that all expmap images
are different.

Namely,

exp_image_3.fit    ----> is an expmap using as a ref point nominal one
		          and all GTIs (as PPS)

exp_image_3_att.fit ---> is an expmap with different ref point (user's
                         ref point)

exp_image_3_obi1_noatt.fit---> is an expmap with nominal ref point
			       and for only observational interval #1

and finally,

exp_image_3_obi1_att.fit ----> is an eexpamp with user's ref point and
			       for only observational interval #1



----
Dr. Nora Loiseau
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