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

From: hayasida@ess.sci.osaka-u.ac.jp
Subject: badpix getotherbadpix=yes
Compose reply
Download message
Move To:
2 replies: 1 2
0 followups:

Private message: yes  no

Notes:

Notification:


Date: Sat, 13 Sep 2003 18:56:50 GMT
From: hayasida@ess.sci.osaka-u.ac.jp
To: xmmhelp@xmm.vilspa.esa.es
Subject: badpix getotherbadpix=yes
Name: Kiyoshi Hayashida

Email_Address: hayasida@ess.sci.osaka-u.ac.jp

Topic: tasks

Other_Topic: 

Usage_Mode: command line

SAS_Release: xmmsas_20030110_1802 - aka 5.4.1

Task_Version: badpix-2.26.3

Type: report a bug

Title: badpix getotherbadpix=yes

Description: I ran emchain in SAS 5.4.1 using the latest set of CCF. I found
that badpixels listed in the CCF file in my case (EMOS1_BADPIX_0015.CCF) was not
put into the event file created. In other word, mode 2 badpixels are not used
even when we specify   getotherbadpix=yes. I put log file of the task badpix. I
am afarid that repeated message of "read-only, and will not be written back to
disk"
might be related to the problem. Could you suggest possible cause of this
problem, something wrong in my usage or software bug ? 

==============

badpix:- Executing (routine): badpix eventset='event01.in' getuplnkbadpix=yes
getotherbadpix=yes getnewbadpix=no badpixset='badpixfind.fits' emptyextension=no
windowfilter=no withoutset=no outset='event01.out'  -V 8
badpix:- badpix (badpix-2.26.3)  [xmmsas_20030110_1802-5.4.1] started: 
2003-09-13T16:58:09.000
.....
.....
badpix:- Data for column with qualified name
/share/newton1/ccf/constituents/EMOS1_BADPIX_0015.CCF:BADPIX:MODE_N/A (column
number is 6) from row 0 to row 283 is read-only, and will not be written back to
disk.
badpix:- Reading data for column with qualified name
/share/newton1/ccf/constituents/EMOS1_BADPIX_0015.CCF:BADPIX:MODE_N/A (column
number is 6) from row 0 to row 283
badpix:- Data for column with qualified name
/share/newton1/ccf/constituents/EMOS1_BADPIX_0015.CCF:BADPIX:MODE_N/A (column
number is 6) from row 0 to row 283 is read-only, and will not be written back to
disk.
badpix:- Reading data for column with qualified name
/share/newton1/ccf/constituents/EMOS1_BADPIX_0015.CCF:BADPIX:MODE_N/A (column
number is 6) from row 0 to row 283
....
....
badpix:- Request to close the dataset with name
'/share/newton1/ccf/constituents/EMOS1_BADPIX_0015.CCF'.  There are currently 2
datasets in memory
badpix:- Attempting to close the fits file with name
'/share/newton1/ccf/constituents/EMOS1_BADPIX_0015.CCF'. If successful there
will be 0 fits files remaining open.
badpix:- The dataset with name
'/share/newton1/ccf/constituents/EMOS1_BADPIX_0015.CCF' was closed successfully.
badpix:-  CCF contains  11  bad pixel sets
badpix:-  11  mode1 pixel sets (uplinked to the satelite)
badpix:-  - Contained within ODF files
badpix:-  0  mode2 pixel sets (not uplinked to the satelite)
badpix:-  11  pixel sets in total
badpix:-    X    Y  TYPE  Y-EXTENT  MODE
badpix:-   181  276    1       1       1
badpix:-   239  384    1       1       1
...



Operating_System: RedHat 9

Other_Operating_System: TruUnix v4.0

Instrument: emos1

Data_Type: data products

Observation_Identifier: 

Exposure_Identifier: 

Private: 

Submitted_From: 133.1.160.232 (133.1.160.232)

Agent: Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.2.1) Gecko/20030225

Referer: http://xmm.vilspa.esa.es/

Identify: 


Reply 1

Resend
From: Nora Loiseau <xmmhelp@xmm.vilspa.esa.es>
To: hayasida@ess.sci.osaka-u.ac.jp
Subject: Re: badpix getotherbadpix=yes (PR#9148)
Date: Wed Sep 17 09:27:20 2003
Dear Dr. Hayashida,

the SAS support group is investigating your problem, we will come back
to you as soon as it is solved.

Best regards,

Nora

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


Reply 2

Resend
From: Nora Loiseau <xmmhelp@xmm.vilspa.esa.es>
To: hayasida@ess.sci.osaka-u.ac.jp
Subject: Re: badpix getotherbadpix=yes (PR#9148)
Date: Mon Oct  6 08:24:30 2003
Dear Dr. Hayashida
> 
> Description: I ran emchain in SAS 5.4.1 using the latest set of CCF. I
found
> that badpixels listed in the CCF file in my case (EMOS1_BADPIX_0015.CCF)
was
not
> put into the event file created. In other word, mode 2 badpixels are not
used
> even when we specify   getotherbadpix=yes. I put log file of the task
badpix.
I
> am afarid that repeated message of "read-only, and will not be written back
to
> disk"
> might be related to the problem. Could you suggest possible cause of this
> problem, something wrong in my usage or software bug ? 


SAS support informs me that "read-only" is a nominal given that there is no need
to modify this file. There is no badpixel in CCD1, (the information that you
attached is for CCD1), if you analyse CCD6 and CCD7 you will find the
badpixels.
Therefore there is nothing wrong in the reduction of your data.

Best regards,

Nora

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