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 AO19/85558
Full headers

From: j.kaastra@sron.nl
Subject: joint Swift time for anticipated ToO
Compose reply
Download message
Move To:
1 replies: 1
1 followups: 1

Private message: yes  no

Notes:

Notification:


Date: Tue, 20 Aug 2019 10:54:10 +0200
From: j.kaastra@sron.nl
To: xmmhelp@sciops.esa.int
Subject: joint Swift time for anticipated ToO
Full_Name: Jelle Kaastra
Submission from: (NULL) (193.147.152.102)


dear helpdesk colleague,

I have an approved AO18 anticipated ToO program running, that did not yet
trigger. I understand from the rules (section 7.3.2 of the XMM-Newton
ANNOUNCEMENT OF OPPORTUNITY: POLICIES AND PROCEDURES document) that it will be
carried on twice to the next AO until it triggers. Thus, I do not need to
repropose for the XMM-Newton (and joint HST and NuSTAR time). Is that correct?

However, there is also associated Swift time approved by the joint program. This
Swift time is needed to monitor our potential target list in order to find a
possible trigger for XMM-Newton. The amount of approved Swift time is what we
need for one year of monitoring. Hence, it is not sufficient for the next two
XMM-Newton years (if the source has not triggered within the regular AO18 window
that closes May 2020). 

What policy should we follow? Should we re-propose for the Swift time only for
the upcoming Swift cycle (stating that it is associated with our joint XMM-Swift
program) or is there another way to assure that we maintain the Swift monitoring
until we receive a trigger?


Reply 1

Resend
From: Rosario Gonzalez Riestra <xmmhelp@sciops.esa.int>
To: j.kaastra@sron.nl
Subject: Re: joint Swift time for anticipated ToO (PR#85558)
Date: Mon Sep  9 17:36:15 2019
Dear Jelle,

First, apologies for the delay in the answer. We had problems with our mail
system and some mails were lost and we could recover them only now.

I have passed tour question to Norbert. Maybe he'll answer you personally even

Have a nice time in Bolonia

Charo


Followup 1

Compose reply
Download message
From: Jelle Kaastra <J.S.Kaastra@sron.nl>
To: Rosario Gonzalez Riestra <xmmhelp@sciops.esa.int>
Subject: Re: joint Swift time for anticipated ToO (PR#85558)
Date: Mon, 9 Sep 2019 15:38:39 +0000
RGVhciBDaGFybywNCg0KTm8gcHJvYmxlbSwgYWN0dWFsbHkgTm9yYmVydCByZWNlaXZlZCB0aGUg
bWVzc2FnZSB3aGlsZSBoZSB3YXMgc2l0dGluZyBuZXh0IHRvIG1lIGluIEJvbG9nbmEuIFdlIGhh
dmUgZGlzY3Vzc2VkDQp0aGlzIGR1cmluZyB0aGUgdGVhIGJyZWFrLCBhbmQgSSBub3cga25vdyB3
aGF0IHRvIGRvIChyZS1wcm9wb3NlIGZvciBTd2lmdCkuDQoNClRoYW5rcywNCg0KSmVsbGUNCg0K
77u/T24gMDkvMDkvMjAxOSwgMTc6MzYsICJSb3NhcmlvIEdvbnphbGV6IFJpZXN0cmEiIDx4bW1o
ZWxwQHNjaW9wcy5lc2EuaW50PiB3cm90ZToNCg0KICAgIA0KICAgIERlYXIgSmVsbGUsDQogICAg
DQogICAgRmlyc3QsIGFwb2xvZ2llcyBmb3IgdGhlIGRlbGF5IGluIHRoZSBhbnN3ZXIuIFdlIGhh
ZCBwcm9ibGVtcyB3aXRoIG91ciBtYWlsDQogICAgc3lzdGVtIGFuZCBzb21lIG1haWxzIHdlcmUg
bG9zdCBhbmQgd2UgY291bGQgcmVjb3ZlciB0aGVtIG9ubHkgbm93Lg0KICAgIA0KICAgIEkgaGF2
ZSBwYXNzZWQgdG91ciBxdWVzdGlvbiB0byBOb3JiZXJ0LiBNYXliZSBoZSdsbCBhbnN3ZXIgeW91
IHBlcnNvbmFsbHkgZXZlbg0KICAgIA0KICAgIEhhdmUgYSBuaWNlIHRpbWUgaW4gQm9sb25pYQ0K
ICAgIA0KICAgIENoYXJvDQogICAgDQogICAgVGhpcyBtZXNzYWdlIGlzIGludGVuZGVkIG9ubHkg
Zm9yIHRoZSByZWNpcGllbnQocykgbmFtZWQgYWJvdmUuIEl0IG1heSBjb250YWluIHByb3ByaWV0
YXJ5IGluZm9ybWF0aW9uIGFuZC9vcg0KICAgIHByb3RlY3RlZCBjb250ZW50LiBBbnkgdW5hdXRo
b3Jpc2VkIGRpc2Nsb3N1cmUsIHVzZSwgcmV0ZW50aW9uIG9yIGRpc3NlbWluYXRpb24gaXMgcHJv
aGliaXRlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQNCiAgICB0aGlzIGUtbWFpbCBpbiBlcnJvciwg
cGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGltbWVkaWF0ZWx5LiBFU0EgYXBwbGllcyBhcHByb3By
aWF0ZSBvcmdhbmlzYXRpb25hbCBtZWFzdXJlcyB0byBwcm90ZWN0DQogICAgcGVyc29uYWwgZGF0
YSwgaW4gY2FzZSBvZiBkYXRhIHByaXZhY3kgcXVlcmllcywgcGxlYXNlIGNvbnRhY3QgdGhlIEVT
QSBEYXRhIFByb3RlY3Rpb24gT2ZmaWNlciAoZHBvQGVzYS5pbnQpLg0KICAgIA0KICAgIA0KICAg
IA0KDQo=


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