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   SASv18.0   SASv18.0_Installation   SciSim   Simulators_other   Suggestions   Trash   Visibility   XMM-bouncing   XMM-news   XRPS   XSA   esas   incoming  

Logged in as guest

Viewing Data/8777
Full headers

From: Yasushi Ikebe <ikebe@milkyway.gsfc.nasa.gov>
Subject: filter closed data
Compose reply
Download message
Move To:
2 replies: 1 2
3 followups: 1 2 3

Private message: yes  no

Notes:

Notification:


Date: Thu, 03 Jul 2003 15:04:14 -0400 (EDT)
To: xmmhelp@xmm.vilspa.esa.es
Subject: filter closed data
From: Yasushi Ikebe <ikebe@milkyway.gsfc.nasa.gov>
Dear Helpdesk

How can I retrieve EPIC PN and MOS data taken
when the filter wheel was entirly closed.
The data should be representing the background
originated from the high energy particles and gamma-rays.
I know the PN data taken during the Rev 59 are such data.
Are there more data avairable with the same observation condition?

-----------------------------------------------------------------
Yasushi Ikebe Dr.

Office:
Code 661, NASA/Goddard Space Flight Center,
Greenbelt Rd., Greenbelt, MD, 20771, USA
TEL: 301-286-0680
FAX: 301-286-1215

Employer:
Joint Center for Astrophysics, Physics Department,
University of Maryland, Baltimore County, 
1000 Hilltop Circle, Baltimore, MD, 21250, USA
-----------------------------------------------------------------


Reply 1

Resend
From: Michel G. Breitfellner <xmmhelp@xmm.vilspa.esa.es>
To: ikebe@milkyway.gsfc.nasa.gov
Subject: Re: filter closed data (PR#8777)
Date: Tue Jul  8 09:49:18 2003
Dear Dr. Ikebe,

You can get those data directly from the XSA
http://xmm.vilspa.esa.es/external/xmm_data_acc/xsa/index.shtml
using the "Query Specification" form the subsection "Exposures".
There you can specify for each instrument the filters you are
interested in.

I did a test: It took some time to search through all the data
but it worked very well.

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


Followup 1

Compose reply
Download message
Date: Tue, 08 Jul 2003 10:47:33 -0400 (EDT)
To: xmmhelp@xmm.vilspa.esa.es
Subject: Re: filter closed data (PR#8777)
From: Yasushi Ikebe <ikebe@milkyway.gsfc.nasa.gov>
Hi

Thanks for your help.
I succeeded to use the function of XSA.
However, all the filter Closed data with full frame observation mode
turned out to be still in proprietary even they are taken in 2000, 2001.
Why aren't those data public?
If the data base has not been updated, and if you could do so rather soon,
I would be very appreciated.

yasushi
-----------------------------------------------------------------
Yasushi Ikebe Dr.

Office:
Code 661, NASA/Goddard Space Flight Center,
Greenbelt Rd., Greenbelt, MD, 20771, USA
TEL: 301-286-0680
FAX: 301-286-1215

Employer:
Joint Center for Astrophysics, Physics Department,
University of Maryland, Baltimore County, 
1000 Hilltop Circle, Baltimore, MD, 21250, USA
-----------------------------------------------------------------



From: "Michel G. Breitfellner" <xmmhelp@xmm.vilspa.esa.es>
Subject: Re: filter closed data (PR#8777)
Date: Tue, 8 Jul 2003 09:49:15 GMT

> Dear Dr. Ikebe,
> 
> You can get those data directly from the XSA
> http://xmm.vilspa.esa.es/external/xmm_data_acc/xsa/index.shtml
> using the "Query Specification" form the subsection "Exposures".
> There you can specify for each instrument the filters you are
> interested in.
> 
> I did a test: It took some time to search through all the data
> but it worked very well.
> 
> With best regards,
> Michel G. Breitfellner
> XMM-Newton User Support
> 



Reply 2

Resend
From: Norbert Schartel <xmmhelp@xmm.vilspa.esa.es>
To: ikebe@milkyway.gsfc.nasa.gov
Subject: Re: filter closed data (PR#8777)
Date: Mon Jul 14 09:17:29 2003
ear Dr. Ikebe,

the data rights are handled on the basis of ODFs
of observations which included the closed exposures.
Therefore either a complete ODF including all
exposures is public or the complete ODF, including
also the closed filter observations, is protected.

Unfortunately, we started with regular closed observations
very late in the mission, which explains why you find
most of the data still protected.

Please, select the observations in the archive with
Observation Availability:  Proprietary Period Expired

Using this option you will get a list of all observations
which fulfill you requirement and which are public.

With best regards
Norbert




Followup 2

Compose reply
Download message
Date: Mon, 14 Jul 2003 15:18:28 +0200 (MET DST)
From: Mail Delivery Subsystem <MAILER-DAEMON@esacom51-int.vilspa.esa.int>
To: <xmmhelp@xmm.vilspa.esa.es>
Subject: Warning: could not send message for past 4 hours
This is a MIME-encapsulated message

--h6EDEg7E024798.1058188708/esacom51.vilspa.esa.int

    **********************************************
    **      THIS IS A WARNING MESSAGE ONLY      **
    **  YOU DO NOT NEED TO RESEND YOUR MESSAGE  **
    **********************************************

The original message was received at Mon, 14 Jul 2003 11:18:03 +0200 (MET DST)
from xvsas01.vilspa.esa.es [193.147.152.101]

   ----- Transcript of session follows -----
<mgb@hadron.info>... Deferred: Connection refused by ns1.hadron.info.
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old

--h6EDEg7E024798.1058188708/esacom51.vilspa.esa.int
Content-Type: message/delivery-status

Reporting-MTA: dns; esacom51.vilspa.esa.int
Arrival-Date: Mon, 14 Jul 2003 11:18:03 +0200 (MET DST)

Final-Recipient: RFC822; mgb@hadron.info
Action: delayed
Status: 4.4.1
Remote-MTA: DNS; ns1.hadron.info
Last-Attempt-Date: Mon, 14 Jul 2003 15:18:28 +0200 (MET DST)
Will-Retry-Until: Sat, 19 Jul 2003 11:18:03 +0200 (MET DST)

--h6EDEg7E024798.1058188708/esacom51.vilspa.esa.int
Content-Type: text/rfc822-headers

Return-Path: <xmmhelp@xmm.vilspa.esa.es>
Received: from xvsas01.vilspa.esa.es (xvsas01.vilspa.esa.es [193.147.152.101])
	by esacom51.vilspa.esa.int (8.12.9/8.12.9/ESA-External-v3.2) with ESMTP id
h6E9I3u1020761
	for <mgb@hadron.info>; Mon, 14 Jul 2003 11:18:03 +0200 (MET DST)
Received: from esacom51.vilspa.esa.int (esacom51-ext.vilspa.esa.int
[192.171.2.19])
	by xvsas01.vilspa.esa.es (8.12.9/8.12.9) with ESMTP id h6E9HriV005836
	for <mbreitfe@xvsas01.vilspa.esa.es>; Mon, 14 Jul 2003 09:17:53 GMT
Received: from xvsoc01.vilspa.esa.es (xvsoc01.vilspa.esa.es [193.147.152.102])
	by esacom51.vilspa.esa.int (8.12.9/8.12.9/ESA-External-v3.2) with ESMTP id
h6E9Hlu1020755
	for <mbreitfe@xvsas01.vilspa.esa.es>; Mon, 14 Jul 2003 11:17:47 +0200
(MET DST)
Received: from localhost (localhost [127.0.0.1])
	by xvsoc01.vilspa.esa.es (8.12.9/8.12.9) with ESMTP id h6E9Hf0c011982
	for <mbreitfe@xmm.vilspa.esa.es>; Mon, 14 Jul 2003 09:17:42 GMT
Date: Mon, 14 Jul 2003 09:17:41 GMT
Message-Id: <200307140917.h6E9Hf0c011982@xvsoc01.vilspa.esa.es>
From: xmmhelp@xmm.vilspa.esa.es
To: mbreitfe@xmm.vilspa.esa.es
Subject: Notification: PR#8777
X-Notification: xmmhelp@xmm.vilspa.esa.es

--h6EDEg7E024798.1058188708/esacom51.vilspa.esa.int--



Followup 3

Compose reply
Download message
Date: Sat, 19 Jul 2003 11:18:42 +0200 (MET DST)
From: Mail Delivery Subsystem <MAILER-DAEMON@esacom51-int.vilspa.esa.int>
To: <xmmhelp@xmm.vilspa.esa.es>
Subject: Returned mail: see transcript for details
This is a MIME-encapsulated message

--h6J7HPoN001798.1058606322/esacom51.vilspa.esa.int

The original message was received at Mon, 14 Jul 2003 11:18:03 +0200 (MET DST)
from xvsas01.vilspa.esa.es [193.147.152.101]

   ----- The following addresses had permanent fatal errors -----
<mgb@hadron.info>

   ----- Transcript of session follows -----
451 hadron.info: Name server timeout
Message could not be delivered for 5 days
Message will be deleted from queue
554 5.0.0 MX list for mail-xgw.vilspa.esa.int points back to
esacom51.vilspa.esa.int

--h6J7HPoN001798.1058606322/esacom51.vilspa.esa.int
Content-Type: message/delivery-status

Reporting-MTA: dns; esacom51.vilspa.esa.int
Arrival-Date: Mon, 14 Jul 2003 11:18:03 +0200 (MET DST)

Final-Recipient: RFC822; mgb@hadron.info
Action: failed
Status: 4.4.7
Last-Attempt-Date: Sat, 19 Jul 2003 11:18:42 +0200 (MET DST)

--h6J7HPoN001798.1058606322/esacom51.vilspa.esa.int
Content-Type: text/rfc822-headers

Return-Path: <xmmhelp@xmm.vilspa.esa.es>
Received: from xvsas01.vilspa.esa.es (xvsas01.vilspa.esa.es [193.147.152.101])
	by esacom51.vilspa.esa.int (8.12.9/8.12.9/ESA-External-v3.2) with ESMTP id
h6E9I3u1020761
	for <mgb@hadron.info>; Mon, 14 Jul 2003 11:18:03 +0200 (MET DST)
Received: from esacom51.vilspa.esa.int (esacom51-ext.vilspa.esa.int
[192.171.2.19])
	by xvsas01.vilspa.esa.es (8.12.9/8.12.9) with ESMTP id h6E9HriV005836
	for <mbreitfe@xvsas01.vilspa.esa.es>; Mon, 14 Jul 2003 09:17:53 GMT
Received: from xvsoc01.vilspa.esa.es (xvsoc01.vilspa.esa.es [193.147.152.102])
	by esacom51.vilspa.esa.int (8.12.9/8.12.9/ESA-External-v3.2) with ESMTP id
h6E9Hlu1020755
	for <mbreitfe@xvsas01.vilspa.esa.es>; Mon, 14 Jul 2003 11:17:47 +0200
(MET DST)
Received: from localhost (localhost [127.0.0.1])
	by xvsoc01.vilspa.esa.es (8.12.9/8.12.9) with ESMTP id h6E9Hf0c011982
	for <mbreitfe@xmm.vilspa.esa.es>; Mon, 14 Jul 2003 09:17:42 GMT
Date: Mon, 14 Jul 2003 09:17:41 GMT
Message-Id: <200307140917.h6E9Hf0c011982@xvsoc01.vilspa.esa.es>
From: xmmhelp@xmm.vilspa.esa.es
To: mbreitfe@xmm.vilspa.esa.es
Subject: Notification: PR#8777
X-Notification: xmmhelp@xmm.vilspa.esa.es

--h6J7HPoN001798.1058606322/esacom51.vilspa.esa.int--


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   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