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 Data/85514
Full headers

From: "Roy, Ankur" <ankur_roy@student.uml.edu>
Subject: XMM detected source list
Compose reply
Download message
Move To:
10 replies: 1 2 3 4 5 6 7 8 9 10
9 followups: 1 2 3 4 5 6 7 8 9

Private message: yes  no

Notes:

Notification:


From: "Roy, Ankur" <ankur_roy@student.uml.edu>
To: "xmmhelp@sciops.esa.int" <xmmhelp@sciops.esa.int>
Subject: XMM detected source list
Date: Fri, 2 Aug 2019 16:33:47 +0000
--_000_DM6PR02MB39794B53E4578604DA049BA7CBD90DM6PR02MB3979namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Hi,

I wanted some information about where to find the list for all detected sou=
rces per ObsID. I checked on a PPS file called P*EP*OBSMLI.HTM which has a =
summary of sources.

However, I also found another file called P*EP*SUMM.HTM which gives informa=
tion about all the sources processed. Which one is the right one to use for=
 detected sources?

Thanks again
Ankur



--_000_DM6PR02MB39794B53E4578604DA049BA7CBD90DM6PR02MB3979namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body>
<div align=3D"left">
<div dir=3D"auto" style=3D"direction: ltr; margin: 0; padding: 0; font-fami=
ly: sans-serif; font-size: 11pt; color: black; ">
<br>
</div>
<div dir=3D"auto" style=3D"direction: ltr; margin: 0; padding: 0; font-fami=
ly: sans-serif; font-size: 11pt; color: black; ">
Hi,<br>
</div>
</div>
<div dir=3D"auto" style=3D"direction: ltr; margin: 0; padding: 0; font-fami=
ly: sans-serif; font-size: 11pt; color: black; ">
<br>
</div>
<div align=3D"left">
<div dir=3D"auto" style=3D"direction: ltr; margin: 0; padding: 0; font-fami=
ly: sans-serif; font-size: 11pt; color: black; ">
I wanted some information about where to find the list for all detected sou=
rces per ObsID. I checked on a PPS file called P*EP*OBSMLI.HTM which has a =
summary of sources.<br>
</div>
</div>
<div dir=3D"auto" style=3D"direction: ltr; margin: 0; padding: 0; font-fami=
ly: sans-serif; font-size: 11pt; color: black; ">
<br>
</div>
<div align=3D"left">
<div dir=3D"auto" style=3D"direction: ltr; margin: 0; padding: 0; font-fami=
ly: sans-serif; font-size: 11pt; color: black; ">
However, I also found another file called P*EP*SUMM.HTM which gives informa=
tion about all the sources processed. Which one is the right one to use for=
 detected sources?<br>
</div>
</div>
<div dir=3D"auto" style=3D"direction: ltr; margin: 0; padding: 0; font-fami=
ly: sans-serif; font-size: 11pt; color: black; ">
<br>
</div>
<div align=3D"left">
<div dir=3D"auto" style=3D"direction: ltr; margin: 0; padding: 0; font-fami=
ly: sans-serif; font-size: 11pt; color: black; ">
Thanks again<br>
</div>
<div dir=3D"auto" style=3D"direction: ltr; margin: 0; padding: 0; font-fami=
ly: sans-serif; font-size: 11pt; color: black; ">
Ankur<br>
</div>
</div>
<div dir=3D"auto" style=3D"direction: ltr; margin: 0; padding: 0; font-fami=
ly: sans-serif; font-size: 11pt; color: black; ">
<br>
</div>
<div dir=3D"auto" style=3D"direction: ltr; margin: 0; padding: 0; font-fami=
ly: sans-serif; font-size: 11pt; color: black; ">
<span id=3D"OutlookSignature"></span><br>
</div>
</body>
</html>

--_000_DM6PR02MB39794B53E4578604DA049BA7CBD90DM6PR02MB3979namp_--


Reply 1

Resend
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: ankur_roy@student.uml.edu
Subject: Re: XMM detected source list (PR#85514)
Date: Sat Aug  3 00:14:09 2019
Dear Ankur,

 for the pipeline products, there is a 'bible' available under:
ftp://xmm2.esac.esa.int/pub/odf/data/docs/XMM-SOC-GEN-ICD-0024.pdf
It contains explanations for all file types.

Specifically you ask about the files
   P*EP*OBSMLI.HTM 
and
   P*EP*SUMM.HTM
The first one is described in section 6.5.5.6, the second one seems incomplete,
at least in an example pps directory I don't find such a file:
  ls P*EP*SUMM.HTM
    ls: No match.
If I missed it, please let me know ObsID you are looking at so I can check for
that particular observation.

Perhaps you mean the file P*EP*SUMMAR0000.HTM which is described in Sect.
6.5.8.1.
In any case, you can open the HTM files in a browser, and they should explain
what they contain.

Best wishes,
Jan-Uwe Ness


> 
> Hi,
> 
> I wanted some information about where to find the list for all detected
> sources per ObsID. I checked on a PPS file called P*EP*OBSMLI.HTM which
> has a summary of sources.
> 
> However, I also found another file called P*EP*SUMM.HTM which gives
> information about all the sources processed. Which one is the right one
> to use for detected sources?
> 
> Thanks again
> Ankur


Followup 1

Compose reply
Download message
From: "Roy, Ankur" <ankur_roy@student.uml.edu>
To: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
Subject: Re: XMM detected source list (PR#85514)
Date: Fri, 2 Aug 2019 22:25:59 +0000
--_000_DM6PR02MB3979A386BF747E6788782185CBD90DM6PR02MB3979namp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,
Thanks for the reply. By the second file I actually meant P*EPX*SUMM*.HTM .=
 You can get it by just searching SUMM. It states that this is the observat=
ion summary file and when I tried to look for the sources processed list in=
 it with the image files, I got it fairly accurate.

On the other hand, the other file has lots of other sources and some of the=
m at least visually are not available in the image files. This is why I am =
not sure which one is correct because the latter one has a description like=
 EPIC summary source list.

Ankur

Get Outlook for Android<https://aka.ms/ghei36>

________________________________
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
Sent: Friday, August 2, 2019 6:14:44 PM
To: Roy, Ankur <ankur_roy@student.uml.edu>
Subject: Re: XMM detected source list (PR#85514)

Dear Ankur,

 for the pipeline products, there is a 'bible' available under:
https://urldefense.proofpoint.com/v2/url?u=3Dftp-3A__xmm2.esac.esa.int_pub_=
odf_data_docs_XMM-2DSOC-2DGEN-2DICD-2D0024.pdf&d=3DDwIBAg&c=3DUycKcnKpT5zzK=
pcCVf29TA&r=3Dk967eDxEYWz0uHc3Wprg7iSM-aPdjIk1nChoYznnMns&m=3DbJsFZvmylQC7u=
1MjNj2rh_umGf9l5UrE_IDYwrxH__Q&s=3DyyLxYoqEnMVdisUfehHWt8TeLbuVCY60l3C9dXLo=
CuA&e=3D
It contains explanations for all file types.

Specifically you ask about the files
   P*EP*OBSMLI.HTM
and
   P*EP*SUMM.HTM
The first one is described in section 6.5.5.6, the second one seems incompl=
ete,
at least in an example pps directory I don't find such a file:
  ls P*EP*SUMM.HTM
    ls: No match.
If I missed it, please let me know ObsID you are looking at so I can check =
for
that particular observation.

Perhaps you mean the file P*EP*SUMMAR0000.HTM which is described in Sect.
6.5.8.1.
In any case, you can open the HTM files in a browser, and they should expla=
in
what they contain.

Best wishes,
Jan-Uwe Ness


>
> Hi,
>
> I wanted some information about where to find the list for all detected
> sources per ObsID. I checked on a PPS file called P*EP*OBSMLI.HTM which
> has a summary of sources.
>
> However, I also found another file called P*EP*SUMM.HTM which gives
> information about all the sources processed. Which one is the right one
> to use for detected sources?
>
> Thanks again
> Ankur

This message is intended only for the recipient(s) named above. It may cont=
ain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemina=
tion is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies app=
ropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data=
 Protection Officer (dpo@esa.int).



--_000_DM6PR02MB3979A386BF747E6788782185CBD90DM6PR02MB3979namp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote {
margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0; font-family:=
sans-serif; font-size:11pt; color:black">
Hi, <br>
</div>
<div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0; font-family:=
sans-serif; font-size:11pt; color:black">
Thanks for the reply. By the second file I actually meant P*EPX*SUMM*.HTM .=
 You can get it by just searching SUMM. It states that this is the observat=
ion summary file and when I tried to look for the sources processed list in=
 it with the image files, I got
 it fairly accurate. <br>
<br>
</div>
<div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0; font-family:=
sans-serif; font-size:11pt; color:black">
On the other hand, the other file has lots of other sources and some of the=
m at least visually are not available in the image files. This is why I am =
not sure which one is correct because the latter one has a description like=
 EPIC summary source list.
<br>
<br>
</div>
<div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0; font-family:=
sans-serif; font-size:11pt; color:black">
Ankur <br>
<br>
</div>
<div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0; font-family:=
sans-serif; font-size:11pt; color:black">
<span id=3D"x_OutlookSignature">
<div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0; font-family:=
sans-serif; font-size:11pt; color:black">
Get <a href=3D"https://aka.ms/ghei36">Outlook for
Android&l

Message of length 8839 truncated


Reply 2

Resend
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: ankur_roy@student.uml.edu
Subject: Re: XMM detected source list (PR#85514)
Date: Sat Aug  3 00:58:23 2019
Hi,

ok, I can see the file, it serves as a navigator for products (spectra, light
curves and detection likelihoods etc).

Meanwhile, the other file is only a table with count rates extracted from the
image which can be done for fainter sources as well. Products are only produced
for sources above a certain threshold, so there are more sources in the
P*EP*OBSMLI.HTM file.

Hope that clarifies.

Best regards,
Jan-Uwe


> Hi,
> Thanks for the reply. By the second file I actually meant P*EPX*SUMM*.HTM
.=
>  You can get it by just searching SUMM. It states that this is the
observat=
> ion summary file and when I tried to look for the sources processed list
in=
>  it with the image files, I got it fairly accurate.
> 
> On the other hand, the other file has lots of other sources and some of
the=
> m at least visually are not available in the image files. This is why I am
=
> not sure which one is correct because the latter one has a description
like=
>  EPIC summary source list.
> 
> Ankur
> 


Reply 3

Resend
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: ankur_roy@student.uml.edu
Subject: Re: XMM detected source list (PR#85514)
Date: Mon Aug  5 12:33:11 2019
Hi Roy,

 as an additional source of information about source in the field of individual
observations is the XMM-Newton Science Archive (XSA):
   http://nxsa.esac.esa.int/nxsa-web/#search
where you can search for PPS sources in the second column of the panel 'Display
Options'.

Best wishes,
Jan-Uwe Ness
--
   Dr. Jan-Uwe Ness
   XMM-Newton User Support Group
   European Space Astronomy Centre


Followup 2

Compose reply
Download message
From: "Roy, Ankur" <ankur_roy@student.uml.edu>
To: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
Subject: Re: XMM detected source list (PR#85514)
Date: Tue, 13 Aug 2019 04:30:34 +0000
SGVsbG8sDQoNClRoYW5rcyBmb3IgY2xlYXJpbmcgb3V0IG15IGRvdWJ0LiBJIGRpZCBoYXZlIG9u
ZSBtb3JlIHF1ZXN0aW9uLiBGb3Igc29tZSBPYnMgSWRzLCBJIGFtIGdldHRpbmcgc29tZSBnYXBz
IGluIHRoZSBuZXQgbGlnaHQgY3VydmUgZXZlbiBhZnRlciBwZXJmb3JtaW5nIGd0aSBmaWx0ZXJp
bmcodXNpbmcgYSB0aHJlc2hvbGQgb2YgMC40Y3RzL3NlYykuDQpJcyB0aGlzIGJlY2F1c2Ugb2Yg
dGVsZW1ldHJ5IHNhdHVyYXRpb24gb3Igc29tZSBpbnN0cnVtZW50YWwgZXJyb3IuIEZvciB0aGVz
ZSBmaXRzIGZpbGVzLCBJIGFtIGdldHRpbmcgbnVsbCB2YWx1ZXMgZm9yIFJhdGUgYXQgbXVsdGlw
bGUgdGltZSBpbnRlcnZhbHMuDQoNCldoYXQgZG8geW91IHRoaW5rIHNob3VsZCBiZSBkb25lIGFu
ZCB3aGF0IGlzIHRoZSByZWFzb24gZm9yIGl0Pw0KDQpBbmt1cg0KDQoNCu+7v09uIDgvMi8xOSwg
Njo1OCBQTSwgIkphbi1Vd2UgTmVzcyIgPHhtbWhlbHBAc2Npb3BzLmVzYS5pbnQ+IHdyb3RlOg0K
DQogICAgSGksDQogICAgDQogICAgb2ssIEkgY2FuIHNlZSB0aGUgZmlsZSwgaXQgc2VydmVzIGFz
IGEgbmF2aWdhdG9yIGZvciBwcm9kdWN0cyAoc3BlY3RyYSwgbGlnaHQNCiAgICBjdXJ2ZXMgYW5k
IGRldGVjdGlvbiBsaWtlbGlob29kcyBldGMpLg0KICAgIA0KICAgIE1lYW53aGlsZSwgdGhlIG90
aGVyIGZpbGUgaXMgb25seSBhIHRhYmxlIHdpdGggY291bnQgcmF0ZXMgZXh0cmFjdGVkIGZyb20g
dGhlDQogICAgaW1hZ2Ugd2hpY2ggY2FuIGJlIGRvbmUgZm9yIGZhaW50ZXIgc291cmNlcyBhcyB3
ZWxsLiBQcm9kdWN0cyBhcmUgb25seSBwcm9kdWNlZA0KICAgIGZvciBzb3VyY2VzIGFib3ZlIGEg
Y2VydGFpbiB0aHJlc2hvbGQsIHNvIHRoZXJlIGFyZSBtb3JlIHNvdXJjZXMgaW4gdGhlDQogICAg
UCpFUCpPQlNNTEkuSFRNIGZpbGUuDQogICAgDQogICAgSG9wZSB0aGF0IGNsYXJpZmllcy4NCiAg
ICANCiAgICBCZXN0IHJlZ2FyZHMsDQogICAgSmFuLVV3ZQ0KICAgIA0KICAgIA0KICAgID4gSGks
DQogICAgPiBUaGFua3MgZm9yIHRoZSByZXBseS4gQnkgdGhlIHNlY29uZCBmaWxlIEkgYWN0dWFs
bHkgbWVhbnQgUCpFUFgqU1VNTSouSFRNIC49DQogICAgPiAgWW91IGNhbiBnZXQgaXQgYnkganVz
dCBzZWFyY2hpbmcgU1VNTS4gSXQgc3RhdGVzIHRoYXQgdGhpcyBpcyB0aGUgb2JzZXJ2YXQ9DQog
ICAgPiBpb24gc3VtbWFyeSBmaWxlIGFuZCB3aGVuIEkgdHJpZWQgdG8gbG9vayBmb3IgdGhlIHNv
dXJjZXMgcHJvY2Vzc2VkIGxpc3QgaW49DQogICAgPiAgaXQgd2l0aCB0aGUgaW1hZ2UgZmlsZXMs
IEkgZ290IGl0IGZhaXJseSBhY2N1cmF0ZS4NCiAgICA+IA0KICAgID4gT24gdGhlIG90aGVyIGhh
bmQsIHRoZSBvdGhlciBmaWxlIGhhcyBsb3RzIG9mIG90aGVyIHNvdXJjZXMgYW5kIHNvbWUgb2Yg
dGhlPQ0KICAgID4gbSBhdCBsZWFzdCB2aXN1YWxseSBhcmUgbm90IGF2YWlsYWJsZSBpbiB0aGUg
aW1hZ2UgZmlsZXMuIFRoaXMgaXMgd2h5IEkgYW0gPQ0KICAgID4gbm90IHN1cmUgd2hpY2ggb25l
IGlzIGNvcnJlY3QgYmVjYXVzZSB0aGUgbGF0dGVyIG9uZSBoYXMgYSBkZXNjcmlwdGlvbiBsaWtl
PQ0KICAgID4gIEVQSUMgc3VtbWFyeSBzb3VyY2UgbGlzdC4NCiAgICA+IA0KICAgID4gQW5rdXIN
CiAgICA+IA0KICAgIA0KICAgIFRoaXMgbWVzc2FnZSBpcyBpbnRlbmRlZCBvbmx5IGZvciB0aGUg
cmVjaXBpZW50KHMpIG5hbWVkIGFib3ZlLiBJdCBtYXkgY29udGFpbiBwcm9wcmlldGFyeSBpbmZv
cm1hdGlvbiBhbmQvb3INCiAgICBwcm90ZWN0ZWQgY29udGVudC4gQW55IHVuYXV0aG9yaXNlZCBk
aXNjbG9zdXJlLCB1c2UsIHJldGVudGlvbiBvciBkaXNzZW1pbmF0aW9uIGlzIHByb2hpYml0ZWQu
IElmIHlvdSBoYXZlIHJlY2VpdmVkDQogICAgdGhpcyBlLW1haWwgaW4gZXJyb3IsIHBsZWFzZSBu
b3RpZnkgdGhlIHNlbmRlciBpbW1lZGlhdGVseS4gRVNBIGFwcGxpZXMgYXBwcm9wcmlhdGUgb3Jn
YW5pc2F0aW9uYWwgbWVhc3VyZXMgdG8gcHJvdGVjdA0KICAgIHBlcnNvbmFsIGRhdGEsIGluIGNh
c2Ugb2YgZGF0YSBwcml2YWN5IHF1ZXJpZXMsIHBsZWFzZSBjb250YWN0IHRoZSBFU0EgRGF0YSBQ
cm90ZWN0aW9uIE9mZmljZXIgKGRwb0Blc2EuaW50KS4NCiAgICANCiAgICANCiAgICANCg0K



Reply 4

Resend
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: ankur_roy@student.uml.edu
Subject: Re: XMM detected source list (PR#85514)
Date: Tue Aug 13 09:36:35 2019
Dear Ankur,

 when you do gti (*good* time interval) filtering you will certainly get gaps in
the light curve during the respective *bad* time intervals. gti filtering is
more important for generating spectra.
But it sounds like you also get them without gti filtering. Since you are
looking at net light curves, there may be particularly high background. You can
check that by looking at the raw light curves extracted from source extraction
region and background extraction region, respectively. If you see strange
behaviour in the background light curve at the time of gaps in the net light
curve, that may explain the gaps.

But it depends on the particular observations, if you want me to have a closer
look, you would need to send me one of the ObsIDs.

Best regards,
Jan-Uwe


On 13/8/19 6:30, Roy, Ankur wrote:
> Hello,
>
> Thanks for clearing out my doubt. I did have one more question. For some
Obs
Ids, I am getting some gaps in the net light curve even after performing gti
filtering(using a threshold of 0.4cts/sec).
> Is this because of telemetry saturation or some instrumental error. For
these
fits files, I am getting null values for Rate at multiple time intervals.
>
> What do you think should be done and what is the reason for it?
>
> Ankur
>
>
> &#65279;On 8/2/19, 6:58 PM, "Jan-Uwe Ness"
<xmmhelp@sciops.esa.int> wrote:
>
>     Hi,
>     
>     ok, I can see the file, it serves as a navigator for products (spectra,
light
>     curves and detection likelihoods etc).
>     
>     Meanwhile, the other file is only a table with count rates extracted
from
the
>     image which can be done for fainter sources as well. Products are only
produced
>     for sources above a certain threshold, so there are more sources in
the
>     P*EP*OBSMLI.HTM file.
>     
>     Hope that clarifies.
>     
>     Best regards,
>     Jan-Uwe
>     
>     
>> Hi,
>> Thanks for the reply. By the second file I actually meant
P*EPX*SUMM*.HTM .=
>>  You can get it by just searching SUMM. It states that this is the
observat=
>> ion summary file and when I tried to look for the sources processed
list in=
>>  it with the image files, I got it fairly accurate.
>> 
>> On the other hand, the other file has lots of other sources and some of
the=
>> m at least visually are not available in the image files. This is why I
am =
>> not sure which one is correct because the latter one has a description
like=
>>  EPIC summary source list.
>> 
>> Ankur


Followup 3

Compose reply
Download message
From: "Roy, Ankur" <ankur_roy@student.uml.edu>
To: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
Subject: Re: XMM detected source list (PR#85514)
Date: Thu, 15 Aug 2019 03:09:59 +0000
--_000_BYAPR02MB5447777CD2729B9D57E30289CBAC0BYAPR02MB5447namp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Thanks for the reply. I can definitely send some of the Obs IDs to you. Apa=
rt from this I have this one other error happening in my program.
When I am trying to use epiclccorr on a couple of Obs IDs to extract the ne=
t lc s, I am getting the following error prompt:

epiclccorr: error(attributable not found). Could not find attribute with qu=
alified name src.lc(for example):RATE%EXPOSURE in attribute set RATE

I will be thankful if you can give a solution to this as my I am trying to =
run a script which does all of the above across multiple Obs IDs. And I am =
using the src and bkg lc extraction commands as stated in the XMM analaysis=
 thread.

Ankur

Get Outlook for Android<https://aka.ms/ghei36>

________________________________
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
Sent: Tuesday, August 13, 2019 3:36:41 AM
To: Roy, Ankur <ankur_roy@student.uml.edu>
Subject: Re: XMM detected source list (PR#85514)

Dear Ankur,

 when you do gti (*good* time interval) filtering you will certainly get ga=
ps in
the light curve during the respective *bad* time intervals. gti filtering i=
s
more important for generating spectra.
But it sounds like you also get them without gti filtering. Since you are
looking at net light curves, there may be particularly high background. You=
 can
check that by looking at the raw light curves extracted from source extract=
ion
region and background extraction region, respectively. If you see strange
behaviour in the background light curve at the time of gaps in the net ligh=
t
curve, that may explain the gaps.

But it depends on the particular observations, if you want me to have a clo=
ser
look, you would need to send me one of the ObsIDs.

Best regards,
Jan-Uwe


On 13/8/19 6:30, Roy, Ankur wrote:
> Hello,
>
> Thanks for clearing out my doubt. I did have one more question. For some =
Obs
Ids, I am getting some gaps in the net light curve even after performing gt=
i
filtering(using a threshold of 0.4cts/sec).
> Is this because of telemetry saturation or some instrumental error. For t=
hese
fits files, I am getting null values for Rate at multiple time intervals.
>
> What do you think should be done and what is the reason for it?
>
> Ankur
>
>
> &#65279;On 8/2/19, 6:58 PM, "Jan-Uwe Ness"
<xmmhelp@sciops.esa.int> wrote=
:
>
>     Hi,
>
>     ok, I can see the file, it serves as a navigator for products (spectr=
a,
light
>     curves and detection likelihoods etc).
>
>     Meanwhile, the other file is only a table with count rates extracted =
from
the
>     image which can be done for fainter sources as well. Products are onl=
y
produced
>     for sources above a certain threshold, so there are more sources in t=
he
>     P*EP*OBSMLI.HTM file.
>
>     Hope that clarifies.
>
>     Best regards,
>     Jan-Uwe
>
>
>> Hi,
>> Thanks for the reply. By the second file I actually meant
P*EPX*SUMM*.HT=
M .=3D
>>  You can get it by just searching SUMM. It states that this is the
obser=
vat=3D
>> ion summary file and when I tried to look for the sources processed
list=
 in=3D
>>  it with the image files, I got it fairly accurate.
>>
>> On the other hand, the other file has lots of other sources and some of
=
the=3D
>> m at least visually are not available in the image files. This is why I
=
am =3D
>> not sure which one is correct because the latter one has a description
l=
ike=3D
>>  EPIC summary source list.
>>
>> Ankur

This message is intended only for the recipient(s) named above. It may cont=
ain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemina=
tion is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies app=
ropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data=
 Protection Officer (dpo@esa.int).



--_000_BYAPR02MB5447777CD2729B9D57E30289CBAC0BYAPR02MB5447namp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote {
margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0; font-family:=
sans-serif; font-size:11pt; color:black">
Thanks for the reply. I can definitely send some of the Obs IDs to you. Apa=
rt from this I have this one other error happening in 

Message of length 12145 truncated


Reply 5

Resend
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: ankur_roy@student.uml.edu
Subject: Re: XMM detected source list (PR#85514)
Date: Tue Sep 10 00:43:24 2019
Dear Ankur,

 can you give a little more information what you are doing up to this error
message? It only says that an attribute is missing but not which one, so I need
some more info from you to identify at which step the problem happens.

Best wishes,
Jan-Uwe

> Thanks for the reply. I can definitely send some of the Obs IDs to you.
Apa=
> rt from this I have this one other error happening in my program.
> When I am trying to use epiclccorr on a couple of Obs IDs to extract the
ne=
> t lc s, I am getting the following error prompt:
> 
> epiclccorr: error(attributable not found). Could not find attribute with
qu=
> alified name src.lc(for example):RATE%EXPOSURE in attribute set RATE
> 
> I will be thankful if you can give a solution to this as my I am trying to
=
> run a script which does all of the above across multiple Obs IDs. And I am
=
> using the src and bkg lc extraction commands as stated in the XMM
analaysis=
>  thread.
> 
> Ankur


Followup 4

Compose reply
Download message
From: "Roy, Ankur" <ankur_roy@student.uml.edu>
To: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
Subject: Re: XMM detected source list (PR#85514)
Date: Mon, 9 Sep 2019 22:45:15 +0000
--_000_MN2PR02MB7069C17EA388E1FAEE2555A7CBB70MN2PR02MB7069namp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

This happens on the step of executing the epiclccorr command in order to ge=
t the net light curve.

Get Outlook for Android<https://aka.ms/ghei36>

________________________________
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
Sent: Monday, September 9, 2019 6:43:30 PM
To: Roy, Ankur <ankur_roy@student.uml.edu>
Subject: Re: XMM detected source list (PR#85514)

Dear Ankur,

 can you give a little more information what you are doing up to this error
message? It only says that an attribute is missing but not which one, so I =
need
some more info from you to identify at which step the problem happens.

Best wishes,
Jan-Uwe

> Thanks for the reply. I can definitely send some of the Obs IDs to you. A=
pa=3D
> rt from this I have this one other error happening in my program.
> When I am trying to use epiclccorr on a couple of Obs IDs to extract the =
ne=3D
> t lc s, I am getting the following error prompt:
>
> epiclccorr: error(attributable not found). Could not find attribute with =
qu=3D
> alified name src.lc(for example):RATE%EXPOSURE in attribute set RATE
>
> I will be thankful if you can give a solution to this as my I am trying t=
o =3D
> run a script which does all of the above across multiple Obs IDs. And I a=
m =3D
> using the src and bkg lc extraction commands as stated in the XMM analays=
is=3D
>  thread.
>
> Ankur

This message is intended only for the recipient(s) named above. It may cont=
ain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemina=
tion is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies app=
ropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data=
 Protection Officer (dpo@esa.int).



--_000_MN2PR02MB7069C17EA388E1FAEE2555A7CBB70MN2PR02MB7069namp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote {
margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0; font-family:=
sans-serif; font-size:11pt; color:black">
This happens on the step of executing the epiclccorr command in order to ge=
t the net light curve.<br>
<br>
</div>
<div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0; font-family:=
sans-serif; font-size:11pt; color:black">
<span id=3D"x_OutlookSignature">
<div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0; font-family:=
sans-serif; font-size:11pt; color:black">
Get <a href=3D"https://aka.ms/ghei36">Outlook for
Android</a></div>
</span><br>
</div>
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"x_divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri,
sans-serif" =
color=3D"#000000" style=3D"font-size:11pt"><b>From:</b> Jan-Uwe
Ness &lt;xm=
mhelp@sciops.esa.int&gt;<br>
<b>Sent:</b> Monday, September 9, 2019 6:43:30 PM<br>
<b>To:</b> Roy, Ankur
&lt;ankur_roy@student.uml.edu&gt;<br>
<b>Subject:</b> Re: XMM detected source list (PR#85514)</font>
<div>&nbsp;</div>
</div>
</div>
<font size=3D"2"><span style=3D"font-size:11pt;">
<div class=3D"PlainText">Dear Ankur,<br>
<br>
&nbsp;can you give a little more information what you are doing up to this =
error<br>
message? It only says that an attribute is missing but not which one, so I =
need<br>
some more info from you to identify at which step the problem happens.<br>
<br>
Best wishes,<br>
Jan-Uwe<br>
<br>
&gt; Thanks for the reply. I can definitely send some of the Obs IDs to you=
. Apa=3D<br>
&gt; rt from this I have this one other error happening in my
program.<br>
&gt; When I am trying to use epiclccorr on a couple of Obs IDs to extract t=
he ne=3D<br>
&gt; t lc s, I am getting the following error prompt:<br>
&gt; <br>
&gt; epiclccorr: error(attributable not found). Could not find attribute wi=
th qu=3D<br>
&gt; alified name src.lc(for example):RATE%EXPOSURE in attribute set
RATE<b=
r>
&gt; <br>
&gt; I will be thankful if you can give a solution to this as my I am tryin=
g to =3D<br>
&gt; run a script which does al

Message of length 5919 truncated


Reply 6

Resend
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: ankur_roy@student.uml.edu
Subject: Re: XMM detected source list (PR#85514)
Date: Tue Sep 10 08:59:58 2019
Dear Ankur,

 I suspected that, but I cannot reproduce the error, for me it has so far run
through without problems.

Perhaps you have not produced the raw light curves for source and background
first? I can only speculate. Please have a look at the thread and follow step by
step:
https://www.cosmos.esa.int/web/xmm-newton/sas-thread-timing

Best regards,
Jan-Uwe

> 
> This happens on the step of executing the epiclccorr command in order to
ge=
> t the net light curve.
> 
> Get Outlook for Android<https://aka.ms/ghei36>
> 
> ________________________________
> From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
> Sent: Monday, September 9, 2019 6:43:30 PM
> To: Roy, Ankur <ankur_roy@student.uml.edu>
> Subject: Re: XMM detected source list (PR#85514)
> 
> Dear Ankur,
> 
>  can you give a little more information what you are doing up to this
error
> message? It only says that an attribute is missing but not which one, so I
=
> need
> some more info from you to identify at which step the problem happens.
> 
> Best wishes,
> Jan-Uwe
> 
>> Thanks for the reply. I can definitely send some of the Obs IDs to you.
A=
> pa=3D
>> rt from this I have this one other error happening in my program.
>> When I am trying to use epiclccorr on a couple of Obs IDs to extract
the =
> ne=3D
>> t lc s, I am getting the following error prompt:
>>
>> epiclccorr: error(attributable not found). Could not find attribute
with =
> qu=3D
>> alified name src.lc(for example):RATE%EXPOSURE in attribute set RATE
>>
>> I will be thankful if you can give a solution to this as my I am trying
t=
> o =3D
>> run a script which does all of the above across multiple Obs IDs. And I
a=
> m =3D
>> using the src and bkg lc extraction commands as stated in the XMM
analays=
> is=3D
>>  thread.
>>
>> Ankur
> 


Followup 5

Compose reply
Download message
From: "Roy, Ankur" <ankur_roy@student.uml.edu>
To: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
Subject: Re: XMM detected source list (PR#85514)
Date: Wed, 11 Sep 2019 15:12:03 +0000
--_005_MN2PR02MB7069CF4507E9D4E5AAABDB0DCBB10MN2PR02MB7069namp_
Content-Type: multipart/alternative;
	boundary="_000_MN2PR02MB7069CF4507E9D4E5AAABDB0DCBB10MN2PR02MB7069namp_"

--_000_MN2PR02MB7069CF4507E9D4E5AAABDB0DCBB10MN2PR02MB7069namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Roy, Ankur has shared a OneDrive for Business file with you. To view it, cl=
ick the link below.
<https://studentuml-my.sharepoint.com/:u:/g/personal/ankur_roy_student_uml_=
edu/EQILHX_CayxErtaZhF_JsnsBE0XEu_PscNL7cJzIVkcfqA>
[https://r1.res.office365.com/owa/prem/images/dc-generic_20.png]<https://st=
udentuml-my.sharepoint.com/:u:/g/personal/ankur_roy_student_uml_edu/EQILHX_=
CayxErtaZhF_JsnsBE0XEu_PscNL7cJzIVkcfqA>
pn_clean.fits<https://studentuml-my.sharepoint.com/:u:/g/personal/ankur_roy=
_student_uml_edu/EQILHX_CayxErtaZhF_JsnsBE0XEu_PscNL7cJzIVkcfqA>

Hi,

I did produce source and background lc s but I still got the same error. he=
re I am attaching , my source and bkg light curves along with the pn event =
file. I have used a binning of 0.07s.

Ankur
________________________________
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
Sent: Tuesday, September 10, 2019 3:00 AM
To: Roy, Ankur <ankur_roy@student.uml.edu>
Subject: Re: XMM detected source list (PR#85514)

Dear Ankur,

 I suspected that, but I cannot reproduce the error, for me it has so far r=
un
through without problems.

Perhaps you have not produced the raw light curves for source and backgroun=
d
first? I can only speculate. Please have a look at the thread and follow st=
ep by
step:
https://urldefense.com/v3/__https://www.cosmos.esa.int/web/xmm-newton/sas-t=
hread-timing__;!vt9fxkjPvaI!OYKGtl2YLxXkWJMNsaas4Oi6FRFF7jRRg9eVwUt1k10LjAD=
5lw_8GhXyXM3nS8vznk8AK5o$

Best regards,
Jan-Uwe

>
> This happens on the step of executing the epiclccorr command in order to =
ge=3D
> t the net light curve.
>
> Get Outlook for
Android<https://urldefense.com/v3/__https://aka.ms/ghei36=
__;!vt9fxkjPvaI!OYKGtl2YLxXkWJMNsaas4Oi6FRFF7jRRg9eVwUt1k10LjAD5lw_8GhXyXM3=
nS8vzPR1xzAA$ >
>
> ________________________________
> From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
> Sent: Monday, September 9, 2019 6:43:30 PM
> To: Roy, Ankur <ankur_roy@student.uml.edu>
> Subject: Re: XMM detected source list (PR#85514)
>
> Dear Ankur,
>
>  can you give a little more information what you are doing up to this err=
or
> message? It only says that an attribute is missing but not which one, so =
I =3D
> need
> some more info from you to identify at which step the problem happens.
>
> Best wishes,
> Jan-Uwe
>
>> Thanks for the reply. I can definitely send some of the Obs IDs to you.
=
A=3D
> pa=3D3D
>> rt from this I have this one other error happening in my program.
>> When I am trying to use epiclccorr on a couple of Obs IDs to extract
the=
 =3D
> ne=3D3D
>> t lc s, I am getting the following error prompt:
>>
>> epiclccorr: error(attributable not found). Could not find attribute
with=
 =3D
> qu=3D3D
>> alified name src.lc(for example):RATE%EXPOSURE in attribute set RATE
>>
>> I will be thankful if you can give a solution to this as my I am trying
=
t=3D
> o =3D3D
>> run a script which does all of the above across multiple Obs IDs. And I
=
a=3D
> m =3D3D
>> using the src and bkg lc extraction commands as stated in the XMM
analay=
s=3D
> is=3D3D
>>  thread.
>>
>> Ankur
>

This message is intended only for the recipient(s) named above. It may cont=
ain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemina=
tion is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies app=
ropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data=
 Protection Officer (dpo@esa.int).



--_000_MN2PR02MB7069CF4507E9D4E5AAABDB0DCBB10MN2PR02MB7069namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<style type=3D"text/css" style=3D"display:none;"> P
{margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<!--[if lte mso 15 || CheckWebRef]-->
<div id=3D"OwaReferenceAttachments" contenteditable=3D"false">
<table style=3D"padding-bottom: 13px; border-width: 0px; border-style: none=
;">
<tbody>
<tr valign=3D"top">
<td>
<table style=3D"border-width: 0px 0px 1px 0px; border-color:#C7C7C7; border=
-style: none none dotted none;">
<tbody>
<tr valign=3D"top">
<td style=3D"padding-bottom:7px;">
<table align=3D"left" style=3D"padding-right: 28px; border-width: 0px; back=
g

Message of length 17887223 truncated


Reply 7

Resend
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: ankur_roy@student.uml.edu
Subject: Re: XMM detected source list (PR#85514)
Date: Wed Sep 11 18:53:37 2019
Hi,

 looking at your light curves, I see there are zero counts in all time bins. How
have you chosen the region? In the header I see you have chosen region:
21307.97 25994.52
When looking at the events file, there are no data at these pixel positions.
If you extract from pixel position 28046, 26249 and background something like
26558, 23049, it should work, at least I was able to extract a light curve.

Best regards,
Jan-Uwe


> 
> Hi,
> 
> I did produce source and background lc s but I still got the same error.
he=
> re I am attaching , my source and bkg light curves along with the pn event
=
> file. I have used a binning of 0.07s.
> 
> Ankur
> ________________________________
> From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
> Sent: Tuesday, September 10, 2019 3:00 AM
> To: Roy, Ankur <ankur_roy@student.uml.edu>
> Subject: Re: XMM detected source list (PR#85514)
> 
> Dear Ankur,
> 
>  I suspected that, but I cannot reproduce the error, for me it has so far
r=
> un
> through without problems.
> 
> Perhaps you have not produced the raw light curves for source and
backgroun=
> d
> first? I can only speculate. Please have a look at the thread and follow
st=
> ep by
> step:
> https://urldefense.com/v3/__https://www.cosmos.esa.int/web/xmm-newton/sas-t=
> hread-timing__;!vt9fxkjPvaI!OYKGtl2YLxXkWJMNsaas4Oi6FRFF7jRRg9eVwUt1k10LjAD=
> 5lw_8GhXyXM3nS8vznk8AK5o$
> 
> Best regards,
> Jan-Uwe
> 


Followup 6

Compose reply
Download message
From: "Roy, Ankur" <ankur_roy@student.uml.edu>
To: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
Subject: Re: XMM detected source list (PR#85514)
Date: Wed, 11 Sep 2019 17:23:53 +0000
--_000_MN2PR02MB7069BFF5827F3FD43A9E7A56CBB10MN2PR02MB7069namp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I have chosen the region in the following way:
If suppose I suspect there is a source present in that Obs ID, I use the co=
ordinates of the same and apply them to the image file and extract the pixe=
l coordinates using ecoordconv. Then I use these to extract source light cu=
rves.

Get Outlook for Android<https://aka.ms/ghei36>

________________________________
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
Sent: Wednesday, September 11, 2019 12:53:43 PM
To: Roy, Ankur <ankur_roy@student.uml.edu>
Subject: Re: XMM detected source list (PR#85514)

Hi,

 looking at your light curves, I see there are zero counts in all time bins=
. How
have you chosen the region? In the header I see you have chosen region:
21307.97 25994.52
When looking at the events file, there are no data at these pixel positions=
.
If you extract from pixel position 28046, 26249 and background something li=
ke
26558, 23049, it should work, at least I was able to extract a light curve.

Best regards,
Jan-Uwe


>
> Hi,
>
> I did produce source and background lc s but I still got the same error. =
he=3D
> re I am attaching , my source and bkg light curves along with the pn even=
t =3D
> file. I have used a binning of 0.07s.
>
> Ankur
> ________________________________
> From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
> Sent: Tuesday, September 10, 2019 3:00 AM
> To: Roy, Ankur <ankur_roy@student.uml.edu>
> Subject: Re: XMM detected source list (PR#85514)
>
> Dear Ankur,
>
>  I suspected that, but I cannot reproduce the error, for me it has so far=
 r=3D
> un
> through without problems.
>
> Perhaps you have not produced the raw light curves for source and backgro=
un=3D
> d
> first? I can only speculate. Please have a look at the thread and follow =
st=3D
> ep by
> step:
> https://urldefense.com/v3/__https://www.cosmos.esa.int/web/xmm-newton/sas=
-t=3D
> hread-timing__;!vt9fxkjPvaI!OYKGtl2YLxXkWJMNsaas4Oi6FRFF7jRRg9eVwUt1k10Lj=
AD=3D
> 5lw_8GhXyXM3nS8vznk8AK5o$
>
> Best regards,
> Jan-Uwe
>

This message is intended only for the recipient(s) named above. It may cont=
ain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemina=
tion is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies app=
ropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data=
 Protection Officer (dpo@esa.int).



--_000_MN2PR02MB7069BFF5827F3FD43A9E7A56CBB10MN2PR02MB7069namp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote {
margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0; font-family:=
sans-serif; font-size:11pt; color:black">
I have chosen the region in the following way:<br>
</div>
<div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0; font-family:=
sans-serif; font-size:11pt; color:black">
If suppose I suspect there is a source present in that Obs ID, I use the co=
ordinates of the same and apply them to the image file and extract the pixe=
l coordinates using ecoordconv. Then I use these to extract source light cu=
rves.<br>
<br>
</div>
<div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0; font-family:=
sans-serif; font-size:11pt; color:black">
<span id=3D"x_OutlookSignature">
<div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0; font-family:=
sans-serif; font-size:11pt; color:black">
Get <a href=3D"https://aka.ms/ghei36">Outlook for
Android</a></div>
</span><br>
</div>
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"x_divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri,
sans-serif" =
color=3D"#000000" style=3D"font-size:11pt"><b>From:</b> Jan-Uwe
Ness &lt;xm=
mhelp@sciops.esa.int&gt;<br>
<b>Sent:</b> Wednesday, September 11, 2019 12:53:43 PM<br>
<b>To:</b> Roy, Ankur
&lt;ankur_roy@student.uml.edu&gt;<br>
<b>Subject:</b> Re: XMM detected source list (PR#85514)</font>
<div>&nbsp;</div>
</div>
</div>
<font size=3D"2"><span style=3D"font-size:11pt;">
<div class=3D"PlainText">Hi,<br>
<br>
&nbsp;look

Message of length 7904 truncated


Reply 8

Resend
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: ankur_roy@student.uml.edu
Subject: Re: XMM detected source list (PR#85514)
Date: Wed Sep 11 19:49:09 2019
  Which sky coordinates are you looking for?

 
> I have chosen the region in the following way:
> If suppose I suspect there is a source present in that Obs ID, I use the
co=
> ordinates of the same and apply them to the image file and extract the
pixe=
> l coordinates using ecoordconv. Then I use these to extract source light
cu=
> rves.
> 
> Get Outlook for Android<https://aka.ms/ghei36>
> 
> ________________________________
> From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
> Sent: Wednesday, September 11, 2019 12:53:43 PM
> To: Roy, Ankur <ankur_roy@student.uml.edu>
> Subject: Re: XMM detected source list (PR#85514)
> 
> Hi,
> 
>  looking at your light curves, I see there are zero counts in all time
bins=
> . How
> have you chosen the region? In the header I see you have chosen region:
> 21307.97 25994.52
> When looking at the events file, there are no data at these pixel
positions=
> .
> If you extract from pixel position 28046, 26249 and background something
li=
> ke
> 26558, 23049, it should work, at least I was able to extract a light
curve.
> 
> Best regards,
> Jan-Uwe
> 
> 
>>
>> Hi,
>>
>> I did produce source and background lc s but I still got the same
error. =
> he=3D
>> re I am attaching , my source and bkg light curves along with the pn
even=
> t =3D
>> file. I have used a binning of 0.07s.
>>
>> Ankur
>> ________________________________
>> From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
>> Sent: Tuesday, September 10, 2019 3:00 AM
>> To: Roy, Ankur <ankur_roy@student.uml.edu>
>> Subject: Re: XMM detected source list (PR#85514)
>>
>> Dear Ankur,
>>
>>  I suspected that, but I cannot reproduce the error, for me it has so
far=
>  r=3D
>> un
>> through without problems.
>>
>> Perhaps you have not produced the raw light curves for source and
backgro=
> un=3D
>> d
>> first? I can only speculate. Please have a look at the thread and
follow =
> st=3D
>> ep by
>> step:
>> https://urldefense.com/v3/__https://www.cosmos.esa.int/web/xmm-newton/sas=
> -t=3D
>> hread-timing__;!vt9fxkjPvaI!OYKGtl2YLxXkWJMNsaas4Oi6FRFF7jRRg9eVwUt1k10Lj=
> AD=3D
>> 5lw_8GhXyXM3nS8vznk8AK5o$
>>
>> Best regards,
>> Jan-Uwe
>>
> 
> This message is intended only for the recipient(s) named above. It may
cont=
> ain proprietary information and/or
> protected content. Any unauthorised disclosure, use, retention or
dissemina=
> tion is prohibited. If you have received
> this e-mail in error, please notify the sender immediately. ESA applies
app=
> ropriate organisational measures to protect
> personal data, in case of data privacy queries, please contact the ESA
Data=
>  Protection Officer (dpo@esa.int).
> 
> 
> 
> --_000_MN2PR02MB7069BFF5827F3FD43A9E7A56CBB10MN2PR02MB7069namp_
> Content-Type: text/html; charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> 
> <html>
> <head>
> <meta http-equiv=3D"Content-Type" content=3D"text/html;
charset=3Diso-8859-=
> 1">
> <meta name=3D"Generator" content=3D"Microsoft Exchange Server">
> <!-- converted from text --><style><!-- .EmailQuote {
margin-left: 1pt; pad=
> ding-left: 4pt; border-left: #800000 2px solid; } --></style>
> </head>
> <body>
> <div>
> <div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0;
font-family:=
> sans-serif; font-size:11pt; color:black">
> I have chosen the region in the following way:<br>
> </div>
> <div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0;
font-family:=
> sans-serif; font-size:11pt; color:black">
> If suppose I suspect there is a source present in that Obs ID, I use the
co=
> ordinates of the same and apply them to the image file and extract the
pixe=
> l coordinates using ecoordconv. Then I use these to extract source light
cu=
> rves.<br>
> <br>
> </div>
> <div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0;
font-family:=
> sans-serif; font-size:11pt; color:black">
> <span id=3D"x_OutlookSignature">
> <div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0;
font-family:=
> sans-serif; font-size:11pt; color:black">
> Get <a href=3D"https://aka.ms/ghei36">Outlook for
Android</a></div>
> </span><br>
> </div>
> <hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
> <div id=3D"x_divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri,
sans-serif" =
>

Message of length 8799 truncated


Followup 7

Compose reply
Download message
From: "Roy, Ankur" <ankur_roy@student.uml.edu>
To: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
Subject: Re: XMM detected source list (PR#85514)
Date: Wed, 11 Sep 2019 17:51:36 +0000
--_000_MN2PR02MB706934F8CAED570AD6986FA5CBB10MN2PR02MB7069namp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

The sky coordinates for SXP 327 in this case.

Get Outlook for Android<https://aka.ms/ghei36>

________________________________
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
Sent: Wednesday, September 11, 2019 1:49:15 PM
To: Roy, Ankur <ankur_roy@student.uml.edu>
Subject: Re: XMM detected source list (PR#85514)


  Which sky coordinates are you looking for?


> I have chosen the region in the following way:
> If suppose I suspect there is a source present in that Obs ID, I use the =
co=3D
> ordinates of the same and apply them to the image file and extract the pi=
xe=3D
> l coordinates using ecoordconv. Then I use these to extract source light =
cu=3D
> rves.
>
> Get Outlook for
Android<https://urldefense.com/v3/__https://aka.ms/ghei36=
__;!vt9fxkjPvaI!NfZZTwJtg2UVPI5E4w12ATyHLU7ijWGCKPse9arHL2ID2IVLcbQWR1yPi4j=
Ms1dzObCbn38$ >
>
> ________________________________
> From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
> Sent: Wednesday, September 11, 2019 12:53:43 PM
> To: Roy, Ankur <ankur_roy@student.uml.edu>
> Subject: Re: XMM detected source list (PR#85514)
>
> Hi,
>
>  looking at your light curves, I see there are zero counts in all time bi=
ns=3D
> . How
> have you chosen the region? In the header I see you have chosen region:
> 21307.97 25994.52
> When looking at the events file, there are no data at these pixel positio=
ns=3D
> .
> If you extract from pixel position 28046, 26249 and background something =
li=3D
> ke
> 26558, 23049, it should work, at least I was able to extract a light curv=
e.
>
> Best regards,
> Jan-Uwe
>
>
>>
>> Hi,
>>
>> I did produce source and background lc s but I still got the same
error.=
 =3D
> he=3D3D
>> re I am attaching , my source and bkg light curves along with the pn
eve=
n=3D
> t =3D3D
>> file. I have used a binning of 0.07s.
>>
>> Ankur
>> ________________________________
>> From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
>> Sent: Tuesday, September 10, 2019 3:00 AM
>> To: Roy, Ankur <ankur_roy@student.uml.edu>
>> Subject: Re: XMM detected source list (PR#85514)
>>
>> Dear Ankur,
>>
>>  I suspected that, but I cannot reproduce the error, for me it has so
fa=
r=3D
>  r=3D3D
>> un
>> through without problems.
>>
>> Perhaps you have not produced the raw light curves for source and
backgr=
o=3D
> un=3D3D
>> d
>> first? I can only speculate. Please have a look at the thread and
follow=
 =3D
> st=3D3D
>> ep by
>> step:
>> https://urldefense.com/v3/__https://www.cosmos.esa.int/web/xmm-newton/sa=
s=3D
> -t=3D3D
>> hread-timing__;!vt9fxkjPvaI!OYKGtl2YLxXkWJMNsaas4Oi6FRFF7jRRg9eVwUt1k10L=
j=3D
> AD=3D3D
>> 5lw_8GhXyXM3nS8vznk8AK5o$
>>
>> Best regards,
>> Jan-Uwe
>>
>
> This message is intended only for the recipient(s) named above. It may co=
nt=3D
> ain proprietary information and/or
> protected content. Any unauthorised disclosure, use, retention or dissemi=
na=3D
> tion is prohibited. If you have received
> this e-mail in error, please notify the sender immediately. ESA applies a=
pp=3D
> ropriate organisational measures to protect
> personal data, in case of data privacy queries, please contact the ESA Da=
ta=3D
>  Protection Officer (dpo@esa.int).
>
>
>
> --_000_MN2PR02MB7069BFF5827F3FD43A9E7A56CBB10MN2PR02MB7069namp_
> Content-Type: text/html; charset=3D"iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> <html>
> <head>
> <meta http-equiv=3D3D"Content-Type" content=3D3D"text/html;
charset=3D3Di=
so-8859-=3D
> 1">
> <meta name=3D3D"Generator" content=3D3D"Microsoft Exchange Server">
> <!-- converted from text --><style><!-- .EmailQuote {
margin-left: 1pt; p=
ad=3D
> ding-left: 4pt; border-left: #800000 2px solid; } --></style>
> </head>
> <body>
> <div>
> <div dir=3D3D"auto" style=3D3D"direction:ltr; margin:0; padding:0;
font-f=
amily:=3D
> sans-serif; font-size:11pt; color:black">
> I have chosen the region in the following way:<br>
> </div>
> <div dir=3D3D"auto" style=3D3D"direction:ltr; margin:0; padding:0;
font-f=
amily:=3D
> sans-serif; font-size:11pt; color:black">
> If suppose I suspect there is a source present in that Obs ID, I use the =
co=3D
> ordinates of the same and apply them to the image file and extract the pi=
xe=3D
> l coordinates using ecoordconv. Then I use these to extract source light =
cu=3D
> rves.<br>
> <br>
> </div>
> <div dir

Message of length 26612 truncated


Reply 9

Resend
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: ankur_roy@student.uml.edu
Subject: Re: XMM detected source list (PR#85514)
Date: Wed Sep 11 21:03:17 2019
Hi,

 ok, that explains, this source is outside the Small Window mode in pn.

The source is covered by the MOS1 detector, but I have had a look and it seems
there is no source at the position of SXP 327 which I took from Simbad as:
 	00 52 52.22 -72 17 15.1

Best regards,
Jan-Uwe Ness

> The sky coordinates for SXP 327 in this case.
> 
> Get Outlook for Android<https://aka.ms/ghei36>
> 
> ________________________________
> From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
> Sent: Wednesday, September 11, 2019 1:49:15 PM
> To: Roy, Ankur <ankur_roy@student.uml.edu>
> Subject: Re: XMM detected source list (PR#85514)
> 
> 
>   Which sky coordinates are you looking for?
> 
> 
>> I have chosen the region in the following way:
>> If suppose I suspect there is a source present in that Obs ID, I use
the =
> co=3D
>> ordinates of the same and apply them to the image file and extract the
pi=
> xe=3D
>> l coordinates using ecoordconv. Then I use these to extract source
light =
> cu=3D
>> rves.
>>
>> Get Outlook for
Android<https://urldefense.com/v3/__https://aka.ms/ghei36=
> __;!vt9fxkjPvaI!NfZZTwJtg2UVPI5E4w12ATyHLU7ijWGCKPse9arHL2ID2IVLcbQWR1yPi4j=
> Ms1dzObCbn38$ >
>>
>> ________________________________
>> From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
>> Sent: Wednesday, September 11, 2019 12:53:43 PM
>> To: Roy, Ankur <ankur_roy@student.uml.edu>
>> Subject: Re: XMM detected source list (PR#85514)
>>
>> Hi,
>>
>>  looking at your light curves, I see there are zero counts in all time
bi=
> ns=3D
>> . How
>> have you chosen the region? In the header I see you have chosen
region:
>> 21307.97 25994.52
>> When looking at the events file, there are no data at these pixel
positio=
> ns=3D
>> .
>> If you extract from pixel position 28046, 26249 and background
something =
> li=3D
>> ke
>> 26558, 23049, it should work, at least I was able to extract a light
curv=
> e.
>>
>> Best regards,
>> Jan-Uwe
>>
>>
>>>
>>> Hi,
>>>
>>> I did produce source and background lc s but I still got the same
error.=
>  =3D
>> he=3D3D
>>> re I am attaching , my source and bkg light curves along with the
pn eve=
> n=3D
>> t =3D3D
>>> file. I have used a binning of 0.07s.
>>>
>>> Ankur


Followup 8

Compose reply
Download message
From: "Roy, Ankur" <ankur_roy@student.uml.edu>
To: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
Subject: Re: XMM detected source list (PR#85514)
Date: Wed, 25 Sep 2019 01:39:03 +0000
VGhhbmtzIGZvciB0aGUgY2xhcmlmaWNhdGlvbi4gSSBoYWQgb25lIG1vcmUgcXVlc3Rpb24uIFN1
cHBvc2UgSSBoYXZlIGFuIGltYWdlLCBob3cgZG8gSSBnZXQgdGhlIG5ldCB0b3RhbCBuby4gb2Yg
Y291bnRzIGZvciBhbnkgIHNvdXJjZSBpbiB0aGF0IGltYWdlLg0KRG8gd2UgdXNlIGVyZWdpb25h
bmFseXNlIGNvbW1hbmQ/DQoNCu+7v09uIDkvMTEvMTksIDM6MDMgUE0sICJKYW4tVXdlIE5lc3Mi
IDx4bW1oZWxwQHNjaW9wcy5lc2EuaW50PiB3cm90ZToNCg0KICAgIEhpLA0KICAgIA0KICAgICBv
aywgdGhhdCBleHBsYWlucywgdGhpcyBzb3VyY2UgaXMgb3V0c2lkZSB0aGUgU21hbGwgV2luZG93
IG1vZGUgaW4gcG4uDQogICAgDQogICAgVGhlIHNvdXJjZSBpcyBjb3ZlcmVkIGJ5IHRoZSBNT1Mx
IGRldGVjdG9yLCBidXQgSSBoYXZlIGhhZCBhIGxvb2sgYW5kIGl0IHNlZW1zDQogICAgdGhlcmUg
aXMgbm8gc291cmNlIGF0IHRoZSBwb3NpdGlvbiBvZiBTWFAgMzI3IHdoaWNoIEkgdG9vayBmcm9t
IFNpbWJhZCBhczoNCiAgICAgCTAwIDUyIDUyLjIyIC03MiAxNyAxNS4xDQogICAgDQogICAgQmVz
dCByZWdhcmRzLA0KICAgIEphbi1Vd2UgTmVzcw0KICAgIA0KICAgID4gVGhlIHNreSBjb29yZGlu
YXRlcyBmb3IgU1hQIDMyNyBpbiB0aGlzIGNhc2UuDQogICAgPiANCiAgICA+IEdldCBPdXRsb29r
IGZvciBBbmRyb2lkPGh0dHBzOi8vdXJsZGVmZW5zZS5jb20vdjMvX19odHRwczovL2FrYS5tcy9n
aGVpMzZfXzshdnQ5ZnhralB2YUkhTUpQdnN1N2loVzRMSFBFQTZqYmljQ3MzNUJ4WUJ2em5DcWtD
N1dVb3NJd1NaRElINDdtMVhSNkt1cmNWbE5XODFobXZhTjQkID4NCiAgICA+IA0KICAgID4gX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCiAgICA+IEZyb206IEphbi1Vd2UgTmVzcyA8
eG1taGVscEBzY2lvcHMuZXNhLmludD4NCiAgICA+IFNlbnQ6IFdlZG5lc2RheSwgU2VwdGVtYmVy
IDExLCAyMDE5IDE6NDk6MTUgUE0NCiAgICA+IFRvOiBSb3ksIEFua3VyIDxhbmt1cl9yb3lAc3R1
ZGVudC51bWwuZWR1Pg0KICAgID4gU3ViamVjdDogUmU6IFhNTSBkZXRlY3RlZCBzb3VyY2UgbGlz
dCAoUFIjODU1MTQpDQogICAgPiANCiAgICA+IA0KICAgID4gICBXaGljaCBza3kgY29vcmRpbmF0
ZXMgYXJlIHlvdSBsb29raW5nIGZvcj8NCiAgICA+IA0KICAgID4gDQogICAgPj4gSSBoYXZlIGNo
b3NlbiB0aGUgcmVnaW9uIGluIHRoZSBmb2xsb3dpbmcgd2F5Og0KICAgID4+IElmIHN1cHBvc2Ug
SSBzdXNwZWN0IHRoZXJlIGlzIGEgc291cmNlIHByZXNlbnQgaW4gdGhhdCBPYnMgSUQsIEkgdXNl
IHRoZSA9DQogICAgPiBjbz0zRA0KICAgID4+IG9yZGluYXRlcyBvZiB0aGUgc2FtZSBhbmQgYXBw
bHkgdGhlbSB0byB0aGUgaW1hZ2UgZmlsZSBhbmQgZXh0cmFjdCB0aGUgcGk9DQogICAgPiB4ZT0z
RA0KICAgID4+IGwgY29vcmRpbmF0ZXMgdXNpbmcgZWNvb3JkY29udi4gVGhlbiBJIHVzZSB0aGVz
ZSB0byBleHRyYWN0IHNvdXJjZSBsaWdodCA9DQogICAgPiBjdT0zRA0KICAgID4+IHJ2ZXMuDQog
ICAgPj4NCiAgICA+PiBHZXQgT3V0bG9vayBmb3IgQW5kcm9pZDxodHRwczovL3VybGRlZmVuc2Uu
Y29tL3YzL19faHR0cHM6Ly9ha2EubXMvZ2hlaTM2PQ0KICAgID4gX187IXZ0OWZ4a2pQdmFJIU5m
WlpUd0p0ZzJVVlBJNUU0dzEyQVR5SExVN2lqV0dDS1BzZTlhckhMMklEMklWTGNiUVdSMXlQaTRq
PQ0KICAgID4gTXMxZHpPYkNibjM4JCA+DQogICAgPj4NCiAgICA+PiBfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXw0KICAgID4+IEZyb206IEphbi1Vd2UgTmVzcyA8eG1taGVscEBzY2lv
cHMuZXNhLmludD4NCiAgICA+PiBTZW50OiBXZWRuZXNkYXksIFNlcHRlbWJlciAxMSwgMjAxOSAx
Mjo1Mzo0MyBQTQ0KICAgID4+IFRvOiBSb3ksIEFua3VyIDxhbmt1cl9yb3lAc3R1ZGVudC51bWwu
ZWR1Pg0KICAgID4+IFN1YmplY3Q6IFJlOiBYTU0gZGV0ZWN0ZWQgc291cmNlIGxpc3QgKFBSIzg1
NTE0KQ0KICAgID4+DQogICAgPj4gSGksDQogICAgPj4NCiAgICA+PiAgbG9va2luZyBhdCB5b3Vy
IGxpZ2h0IGN1cnZlcywgSSBzZWUgdGhlcmUgYXJlIHplcm8gY291bnRzIGluIGFsbCB0aW1lIGJp
PQ0KICAgID4gbnM9M0QNCiAgICA+PiAuIEhvdw0KICAgID4+IGhhdmUgeW91IGNob3NlbiB0aGUg
cmVnaW9uPyBJbiB0aGUgaGVhZGVyIEkgc2VlIHlvdSBoYXZlIGNob3NlbiByZWdpb246DQogICAg
Pj4gMjEzMDcuOTcgMjU5OTQuNTINCiAgICA+PiBXaGVuIGxvb2tpbmcgYXQgdGhlIGV2ZW50cyBm
aWxlLCB0aGVyZSBhcmUgbm8gZGF0YSBhdCB0aGVzZSBwaXhlbCBwb3NpdGlvPQ0KICAgID4gbnM9
M0QNCiAgICA+PiAuDQogICAgPj4gSWYgeW91IGV4dHJhY3QgZnJvbSBwaXhlbCBwb3NpdGlvbiAy
ODA0NiwgMjYyNDkgYW5kIGJhY2tncm91bmQgc29tZXRoaW5nID0NCiAgICA+IGxpPTNEDQogICAg
Pj4ga2UNCiAgICA+PiAyNjU1OCwgMjMwNDksIGl0IHNob3VsZCB3b3JrLCBhdCBsZWFzdCBJIHdh
cyBhYmxlIHRvIGV4dHJhY3QgYSBsaWdodCBjdXJ2PQ0KICAgID4gZS4NCiAgICA+Pg0KICAgID4+
IEJlc3QgcmVnYXJkcywNCiAgICA+PiBKYW4tVXdlDQogICAgPj4NCiAgICA+Pg0KICAgID4+Pg0K
ICAgID4+PiBIaSwNCiAgICA+Pj4NCiAgICA+Pj4gSSBkaWQgcHJvZHVjZSBzb3VyY2UgYW5kIGJh
Y2tncm91bmQgbGMgcyBidXQgSSBzdGlsbCBnb3QgdGhlIHNhbWUgZXJyb3IuPQ0KICAgID4gID0z
RA0KICAgID4+IGhlPTNEM0QNCiAgICA+Pj4gcmUgSSBhbSBhdHRhY2hpbmcgLCBteSBzb3VyY2Ug
YW5kIGJrZyBsaWdodCBjdXJ2ZXMgYWxvbmcgd2l0aCB0aGUgcG4gZXZlPQ0KICAgID4gbj0zRA0K
ICAgID4+IHQgPTNEM0QNCiAgICA+Pj4gZmlsZS4gSSBoYXZlIHVzZWQgYSBiaW5uaW5nIG9mIDAu
MDdzLg0KICAgID4+Pg0KICAgID4+PiBBbmt1cg0KICAgIA0KICAgIFRoaXMgbWVzc2FnZSBpcyBp
bnRlbmRlZCBvbmx5IGZvciB0aGUgcmVjaXBpZW50KHMpIG5hbWVkIGFib3ZlLiBJdCBtYXkgY29u
dGFpbiBwcm9wcmlldGFyeSBpbmZvcm1hdGlvbiBhbmQvb3INCiAgICBwcm90ZWN0ZWQgY29udGVu
dC4gQW55IHVuYXV0aG9yaXNlZCBkaXNjbG9zdXJlLCB1c2UsIHJldGVudGlvbiBvciBkaXNzZW1p
bmF0aW9uIGlzIHByb2hpYml0ZWQuIElmIHlvdSBoYXZlIHJlY2VpdmVkDQogICAgdGhpcyBlLW1h
aWwgaW4gZXJyb3IsIHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBpbW1lZGlhdGVseS4gRVNBIGFw
cGxpZXMgYXBwcm9wcmlhdGUgb3JnYW5pc2F0aW9uYWwgbWVhc3VyZXMgdG8gcHJvdGVjdA0KICAg
IHBlcnNvbmFsIGRhdGEsIGluIGNhc2Ugb2YgZGF0YSBwcml2YWN5IHF1ZXJpZXMsIHBsZWFzZSBj
b250YWN0IHRoZSBFU0EgRGF0YSBQcm90ZWN0aW9uIE9mZmljZXIgKGRwb0Blc2EuaW50KS4NCiAg
ICANCiAgICANCiAgICANCg0K



Followup 9

Compose reply
Download message
From: "Roy, Ankur" <ankur_roy@student.uml.edu>
To: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
Subject: Re: XMM detected source list (PR#85514)
Date: Wed, 25 Sep 2019 14:30:19 +0000
QWxzbywgaG93IGRvIHdlIGdvIGFib3V0IGV4dHJhY3RpbmcgdGhlIGxpZ2h0Y3VydmVzIG9mIHBv
aW50IHNvdXJjZXMgZm9yIGNhbWVyYXMgaWYgdGhleSBhcmUgd29ya2luZyBpbiBkaWZmZXJlbnQg
d2luZG93IG1vZGVzKGxpa2UgRVBJQy9wbiBsYXJnZSB3aW5kb3cgbW9kZSkuDQoNClRoZSBlcGlj
bGNjb3JyIHRocmVhZCBqdXN0IGRvZXMgaXQgZm9yIHNtYWxsIHBuIHdpbmRvdyBtb2RlLg0K77u/
T24gOS8xMS8xOSwgMzowMyBQTSwgIkphbi1Vd2UgTmVzcyIgPHhtbWhlbHBAc2Npb3BzLmVzYS5p
bnQ+IHdyb3RlOg0KDQogICAgIA0KDQo=



Reply 10

Resend
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: ankur_roy@student.uml.edu
Subject: Re: XMM detected source list (PR#85514)
Date: Wed Sep 25 16:40:00 2019
Dear Roy,

 the light curve thread for large window mode is the same as for small window
mode. In large window mode it is easier to find a clean background region free
of other sources.

To extract count rates, you can use the multimission upper limit server which
also gives you an upper limit in case a source you are looking for is not
detected:
http://xmmuls.esac.esa.int/upperlimitserver/
If a source is in the catalogue is returns flux and count rate values from the
catalogue.

You can also find count rates of detected sources in the pipeline products.

eregionanalyse optimises the extraction region to maximise signal to noise.

Best regards,
Jan-Uwe

On 25/9/19 16:30, Roy, Ankur wrote:
> Also, how do we go about extracting the lightcurves of point sources for
cameras if they are working in different window modes(like EPIC/pn large window
mode).
>
> The epiclccorr thread just does it for small pn window mode.

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