Up to top level
AO11   AO12   Backgrounds   Calibration   Conference   Data   Docs   EPICMOS   EPICpn   Feedback   Gallery   Misc   OM   Pending   PhD_Theses   Publications   RGS   RadMonitor   SAS_Hardware   SAS_WS   SASv12.0   SASv12.0_Installation   SASv13.0   SASv13.0_Installation   SciSim   Simulators_other   Suggestions   Trash   Visibility   XMM-bouncing   XMM-news   XRPS   XSA   esas   incoming  

Logged in as guest

Viewing Suggestions/20893
Full headers

From: fwh@mpe.mpg.de
Subject: Observation Log Browser
Compose reply
Move To:
3 replies: 1 2 3
2 followups: 1 2

Private message: yes  no

Notes:

Notification:


Date: Fri, 3 Feb 2006 08:56:10 GMT
From: fwh@mpe.mpg.de
To: xmmhelp@xmm.vilspa.esa.es
CC: fwh@mpe.mpg.de
Subject: Observation Log Browser
Full_Name: Frank HAberl
Submission from: (NULL) (130.183.72.76)


I was searching for XMM observations which cover the following position:
RA=00:55:27.7 Dec=-72:10:59 (I knew that it is covered by the observation
with Obsid 0084200101 with an offset of 11 arcmin from the pointing direction).
The log browser however returns this observation only after using a search
radius
of 19 arcmin (18 still does not return it). The help says:
"Search Radius: in fact a search box centered on RA and Dec. Search radius is in
arcminutes." Is there a problem with the search or should one just give the
full
box size? In the latter case it should be better called diameter.


Reply 1

Resend
From: Nora Loiseau <xmmhelp@xmm.vilspa.esa.es>
To: fwh@mpe.mpg.de
Subject: Re: Observation Log Browser (PR#20893)
Date: Fri Feb  3 17:46:32 2006
Dear dr. Haberl,

thank you for reporting this bug. I am asking the responsible
team to fix it.
In fact the Observation Log Browser is more commonly used for 
checking if certain observations were properly performed, or if
some exposure was lost. But in order to check if certain target or
region has been or will be observed I would recommend the use of the
"XMM-Newton Observations Lokator" at:
http://xmm.esac.esa.int/external/xmm_sched/obs_lokator/index.php

Best regards,

Nora

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


Followup 1

Compose reply
Date: Mon, 06 Feb 2006 08:33:42 +0100
From: Frank Haberl <fwh@mpe.mpg.de>
Subject: Re: Observation Log Browser (PR#20893)
To: Nora Loiseau <xmmhelp@xmm.vilspa.esa.es>
Dear Nora,

unfortunately the lokator does not give details of the instrumental setup.
So to check in which modes the EPICs were (important to decide if the position 
of interest was really observed) one needs to go anyway to the log browser.
So I suggest that the lokator should list more information needed to really 
be able to locate a source in the EPIC read-out windows.
Only then the log browser as second step becomes obsolete.

Best regards
Frank

On Friday 03 February 2006 18:46, you wrote:
> Dear dr. Haberl,
> 
> thank you for reporting this bug. I am asking the responsible
> team to fix it.
> In fact the Observation Log Browser is more commonly used for 
> checking if certain observations were properly performed, or if
> some exposure was lost. But in order to check if certain target or
> region has been or will be observed I would recommend the use of the
> "XMM-Newton Observations Lokator" at:
> http://xmm.esac.esa.int/external/xmm_sched/obs_lokator/index.php
> 
> Best regards,
> 
> Nora
> 
> ----
> Dr. Nora Loiseau
> XMM-Newton User Support Group
> 
> 



Reply 2

Resend
From: Nora Loiseau <xmmhelp@xmm.vilspa.esa.es>
To: fwh@mpe.mpg.de
Subject: Re: Observation Log Browser (PR#20893)
Date: Tue Feb  7 13:35:03 2006
Dear Dr. Haberl,

Thank you for your comments, we will try to improve this
situation. In fact the idea was that the people will search the object
or region with the Lokator, and then by clicking on the ObsID
one is connected to the Observation Log Browser, but maybe this
is not obvious...

Thanks,

Nora

> 
> unfortunately the lokator does not give details of the instrumental setup.
> So to check in which modes the EPICs were (important to decide if the
position

> of interest was really observed) one needs to go anyway to the log
browser.
> So I suggest that the lokator should list more information needed to really

> be able to locate a source in the EPIC read-out windows.
> Only then the log browser as second step becomes obsolete.
> 
> Best regards
> Frank
> 
>----
Dr. Nora Loiseau
XMM-Newton User Support Group


Followup 2

Compose reply
Date: Wed, 08 Feb 2006 16:01:44 +0100
From: Frank Haberl <fwh@mpe.mpg.de>
Subject: Re: Observation Log Browser (PR#20893)
To: Nora Loiseau <xmmhelp@xmm.vilspa.esa.es>
Dear Nora,

On Tuesday 07 February 2006 14:35, you wrote:
> Dear Dr. Haberl,
> 
> Thank you for your comments, we will try to improve this
> situation. In fact the idea was that the people will search the object
> or region with the Lokator, and then by clicking on the ObsID
> one is connected to the Observation Log Browser, but maybe this
> is not obvious...

this feature was indeed unknown to me.

Thank you
Frank

> 
> Thanks,
> 
> Nora
> 
> > 
> > unfortunately the lokator does not give details of the instrumental
setup.
> > So to check in which modes the EPICs were (important to decide if the
position
> 
> > of interest was really observed) one needs to go anyway to the log
browser.
> > So I suggest that the lokator should list more information needed to
really 
> > be able to locate a source in the EPIC read-out windows.
> > Only then the log browser as second step becomes obsolete.
> > 
> > Best regards
> > Frank
> > 
> >----
> Dr. Nora Loiseau
> XMM-Newton User Support Group
> 
> 



Reply 3

Resend
From: Nora Loiseau <xmmhelp@xmm.vilspa.esa.es>
To: fwh@mpe.mpg.de
Subject: Re: Observation Log Browser (PR#20893)
Date: Wed Feb  8 16:29:20 2006
 Dear Dr. Haberl,

>> 
>> Thank you for your comments, we will try to improve this
>> situation. In fact the idea was that the people will search the object
>> or region with the Lokator, and then by clicking on the ObsID
>> one is connected to the Observation Log Browser, but maybe this
>> is not obvious...
> 
> this feature was indeed unknown to me.


we just changed the legend for the table one gets from the 
Observations lokator. I hope now it is more clear.

Thank you for your remarks,

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

Up to top level
AO11   AO12   Backgrounds   Calibration   Conference   Data   Docs   EPICMOS   EPICpn   Feedback   Gallery   Misc   OM   Pending   PhD_Theses   Publications   RGS   RadMonitor   SAS_Hardware   SAS_WS   SASv12.0   SASv12.0_Installation   SASv13.0   SASv13.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