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 SASv17.0/83825
Full headers

From: liu@mpe.mpg.de
Subject: which CCF to use when running emldetect on multiple pointings
Compose reply
Download message
Move To:
4 replies: 1 2 3 4
3 followups: 1 2 3

Private message: yes  no

Notes:

Notification:


Date: Fri, 10 Aug 2018 12:09:53 GMT
From: liu@mpe.mpg.de
To: xmmhelp@sciops.esa.int
CC: liu@mpe.mpg.de
Subject: which CCF to use when running emldetect on multiple pointings
Full_Name: Teng Liu
Submission from: (NULL) (193.147.152.102)


"emldetect" could be run on multiple pointings (overlapping observations with
different observing time). Before running this task, we need to set SAS_CCF. But
the CCF files (.cif) generated by "cifbuild" are different between different
pointings. Which one shall I use?

Best regards,
Teng Liu


Reply 1

Resend
From: Nora Loiseau <xmmhelp@sciops.esa.int>
To: liu@mpe.mpg.de
Subject: Re: which CCF to use when running emldetect on multiple pointings (PR#83825)
Date: Fri Aug 10 17:48:54 2018
Dear Dr. Liu,

For your purpose we could ask you to try the following thread
https://www.cosmos.esa.int/web/xmm-newton/sas-thread-src-find-overlap-stepbystep

This is designed for Mosaic observations but can be applied to any set of
observations, renaming the directory prep_mosaic_001 each time, as follows:

1) Assuming that you want to detect sources in Obs1 and Obs2, first of all
proceed to obtain filtered event list, ccf.cif and *SUM.SAS for each
observation.

2) From your Work directory run emosaic-prep for Obs2, this will create the
resulting files in the directory ./prep_mosaic_001.

3) Rename ./prop-mosaic001 to ./prop_mosaic_002

4) From your Work directory run emosaic-prep for Obs1, this will create the
resulting files in the directory ./prop_mosaic_001

5) Run emosaicproc in the directory Work 

emosaicproc \
   pnevlist='prep_mosaic_001/PNevt_P001.ds prep_mosaic_002/PNevt_P002.ds \
   mos1evlist='prep_mosaic_001/MOS1evt_P001.ds prep_mosaic_002/MOS1evt_P002.ds
\
   mos2evlist='prep_mosaic_001/MOS2evt_P001.ds prep_mosaic_002/MOS2evt_P002.ds'

6) follow the rest of the thread.

Best regards,

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


Followup 1

Compose reply
Download message
From: Teng Liu <liu@mpe.mpg.de>
Date: Mon, 13 Aug 2018 09:47:59 +0200
Subject: Re: which CCF to use when running emldetect on multiple pointings (PR#83825)
To: Nora Loiseau <xmmhelp@sciops.esa.int>
--000000000000bc06e605734c5105
Content-Type: text/plain; charset="UTF-8"

Dear Mr. Nora Loiseau,

Thank you for your reply. I checked the PERL source code of emosaicproc,
which you suggested to use. I am not good at the PERL language. But seems
the emosaicproc is not setting any cif before running emldetect, and
therefore likely the cif of the last pointing in the loop is used by
emldetect. Is it true?

Best regards,
Teng Liu

On Fri, Aug 10, 2018 at 7:48 PM, Nora Loiseau <xmmhelp@sciops.esa.int>
wrote:

> Dear Dr. Liu,
>
> For your purpose we could ask you to try the following thread
> https://www.cosmos.esa.int/web/xmm-newton/sas-thread-src-
> find-overlap-stepbystep
>
> This is designed for Mosaic observations but can be applied to any set of
> observations, renaming the directory prep_mosaic_001 each time, as follows:
>
> 1) Assuming that you want to detect sources in Obs1 and Obs2, first of all
> proceed to obtain filtered event list, ccf.cif and *SUM.SAS for each
> observation.
>
> 2) From your Work directory run emosaic-prep for Obs2, this will create the
> resulting files in the directory ./prep_mosaic_001.
>
> 3) Rename ./prop-mosaic001 to ./prop_mosaic_002
>
> 4) From your Work directory run emosaic-prep for Obs1, this will create the
> resulting files in the directory ./prop_mosaic_001
>
> 5) Run emosaicproc in the directory Work
>
> emosaicproc \
>    pnevlist='prep_mosaic_001/PNevt_P001.ds prep_mosaic_002/PNevt_P002.ds \
>    mos1evlist='prep_mosaic_001/MOS1evt_P001.ds
> prep_mosaic_002/MOS1evt_P002.ds
> \
>    mos2evlist='prep_mosaic_001/MOS2evt_P001.ds
> prep_mosaic_002/MOS2evt_P002.ds'
>
> 6) follow the rest of the thread.
>
> Best regards,
>
> Nora
> ----
> Dr. Nora Loiseau
> XMM-Newton User Support Group
>
> This message is intended only for the recipient(s) named above. It may
> contain proprietary information and/or
> protected content. Any unauthorised disclosure, use, retention or
> dissemination is prohibited. If you have received
> this e-mail in error, please notify the sender immediately. ESA applies
> appropriate organisational measures to protect
> personal data, in case of data privacy queries, please contact the ESA
> Data Protection Officer (dpo@esa.int).
>
>
>

--000000000000bc06e605734c5105
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear Mr. Nora
Loiseau,<div><br></div><div>Thank you for yo=
ur reply. I checked the PERL source code of emosaicproc, which you suggeste=
d to use. I am not good at the PERL language. But seems the emosaicproc is =
not setting any cif before running emldetect, and therefore likely the cif =
of the last pointing in the loop is used by emldetect. Is it
true?</div><di=
v><br></div><div>Best regards,</div><div>Teng
Liu</div></div><div class=3D"=
gmail_extra"><br><div class=3D"gmail_quote">On Fri, Aug 10, 2018
at 7:48 PM=
, Nora Loiseau <span dir=3D"ltr">&lt;<a
href=3D"mailto:xmmhelp@sciops.esa.i=
nt" target=3D"_blank">xmmhelp@sciops.esa.int</a>&gt;</span>
wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex">Dear Dr. Liu,<br>
<br>
For your purpose we could ask you to try the following thread<br>
<a href=3D"https://www.cosmos.esa.int/web/xmm-newton/sas-thread-src-find-ov=
erlap-stepbystep" rel=3D"noreferrer" target=3D"_blank">https://www.cosmos.e=
sa.int/<wbr>web/xmm-newton/sas-thread-src-<wbr>find-overlap-stepbystep</a><=
br>
<br>
This is designed for Mosaic observations but can be applied to any set of<b=
r>
observations, renaming the directory prep_mosaic_001 each time, as follows:=
<br>
<br>
1) Assuming that you want to detect sources in Obs1 and Obs2, first of all<=
br>
proceed to obtain filtered event list, ccf.cif and *SUM.SAS for each<br>
observation.<br>
<br>
2) From your Work directory run emosaic-prep for Obs2, this will create the=
<br>
resulting files in the directory ./prep_mosaic_001.<br>
<br>
3) Rename ./prop-mosaic001 to ./prop_mosaic_002<br>
<br>
4) From your Work directory run emosaic-prep for Obs1, this will create the=
<br>
resulting files in the directory ./prop_mosaic_001<br>
<br>
5) Run emosaicproc in the directory Work <br>
<br>
emosaicproc \<br>
=C2=A0 =C2=A0pnevlist=3D&#39;prep_mosaic_001/<wbr>PNevt_P001.ds
prep_mosaic=
_002/PNevt_P002.ds \<br>
=C2=A0 =C2=A0mos1evlist=3D&#39;prep_mosaic_001/<wbr>MOS1evt_P001.ds
prep_mo=
saic_002/MOS1evt_P002.<wbr>ds<br>
\<br>
=C2=A0 =C2=A0mos2evlist=3D&#39;prep_mo

Message of length 6046 truncated


Reply 2

Resend
From: Nora Loiseau <xmmhelp@sciops.esa.int>
To: liu@mpe.mpg.de
Subject: Re: which CCF to use when running emldetect on multiple pointings (PR#83825)
Date: Mon Aug 13 10:02:57 2018
Dear Teng,

It is not clear looking at the code, but please check the log of the tasks
performed and you will see that the proper ccf are applied.

Best regards,

Nora


> Thank you for your reply. I checked the PERL source code of emosaicproc,
> which you suggested to use. I am not good at the PERL language. But seems
> the emosaicproc is not setting any cif before running emldetect, and
> therefore likely the cif of the last pointing in the loop is used by
> emldetect. Is it true?
> 
> Best regards,
> Teng Liu
> 
> On Fri, Aug 10, 2018 at 7:48 PM, Nora Loiseau
<xmmhelp@sciops.esa.int>
> wrote:
> 
>> Dear Dr. Liu,
>>
>> For your purpose we could ask you to try the following thread
>> https://www.cosmos.esa.int/web/xmm-newton/sas-thread-src-
>> find-overlap-stepbystep
>>
>> This is designed for Mosaic observations but can be applied to any set
of
>> observations, renaming the directory prep_mosaic_001 each time, as
follows:
>>
>> 1) Assuming that you want to detect sources in Obs1 and Obs2, first of
all
>> proceed to obtain filtered event list, ccf.cif and *SUM.SAS for each
>> observation.
>>
>> 2) From your Work directory run emosaic-prep for Obs2, this will create
the
>> resulting files in the directory ./prep_mosaic_001.
>>
>> 3) Rename ./prop-mosaic001 to ./prop_mosaic_002
>>
>> 4) From your Work directory run emosaic-prep for Obs1, this will create
the
>> resulting files in the directory ./prop_mosaic_001
>>
>> 5) Run emosaicproc in the directory Work
>>
>> emosaicproc \
>>    pnevlist='prep_mosaic_001/PNevt_P001.ds
prep_mosaic_002/PNevt_P002.ds \
>>    mos1evlist='prep_mosaic_001/MOS1evt_P001.ds
>> prep_mosaic_002/MOS1evt_P002.ds
>> \
>>    mos2evlist='prep_mosaic_001/MOS2evt_P001.ds
>> prep_mosaic_002/MOS2evt_P002.ds'
>>
>> 6) follow the rest of the thread.
>>
>> Best regards,
>>
>> Nora
>> ----
>> Dr. Nora Loiseau
>> XMM-Newton User Support Group
>>
>> This message is intended only for the recipient(s) named above. It may
>> contain proprietary information and/or
>> protected content. Any unauthorised disclosure, use, retention or
>> dissemination is prohibited. If you have received
>> this e-mail in error, please notify the sender immediately. ESA
applies
>> appropriate organisational measures to protect
>> personal data, in case of data privacy queries, please contact the ESA
>> Data Protection Officer (dpo@esa.int).
>>
>>
>>
> 
> --000000000000bc06e605734c5105
> Content-Type: text/html; charset="UTF-8"
> Content-Transfer-Encoding: quoted-printable
> 
> <div dir=3D"ltr">Dear Mr. Nora
Loiseau,<div><br></div><div>Thank you for yo=
> ur reply. I checked the PERL source code of emosaicproc, which you
suggeste=
> d to use. I am not good at the PERL language. But seems the emosaicproc is
=
> not setting any cif before running emldetect, and therefore likely the cif
=
> of the last pointing in the loop is used by emldetect. Is it
true?</div><di=
> v><br></div><div>Best
regards,</div><div>Teng Liu</div></div><div
class=3D"=
> gmail_extra"><br><div class=3D"gmail_quote">On Fri, Aug 10,
2018 at 7:48 PM=
> , Nora Loiseau <span dir=3D"ltr"><<a
href=3D"mailto:xmmhelp@sciops.esa.i=
> nt" target=3D"_blank">xmmhelp@sciops.esa.int</a>></span>
wrote:<br><bloc=
> kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px
#cc=
> c solid;padding-left:1ex">Dear Dr. Liu,<br>
> <br>
> For your purpose we could ask you to try the following thread<br>
> <a href=3D"https://www.cosmos.esa.int/web/xmm-newton/sas-thread-src-find-ov=
> erlap-stepbystep" rel=3D"noreferrer"
target=3D"_blank">https://www.cosmos.e=
> sa.int/<wbr>web/xmm-newton/sas-thread-src-<wbr>find-overlap-stepbystep</a><=
> br>
> <br>
> This is designed for Mosaic observations but can be applied to any set
of<b=
> r>
> observations, renaming the directory prep_mosaic_001 each time, as
follows:=
> <br>
> <br>
> 1) Assuming that you want to detect sources in Obs1 and Obs2, first of
all<=
> br>
> proceed to obtain filtered event list, ccf.cif and *SUM.SAS for
each<br>
> observation.<br>
> <br>
> 2) From your Work directory run emosaic-prep for Obs2, this will create
the=
> <br>
> resulting files in the directory ./prep_mosaic_001.<br>
> <br>

Message of length 6934 truncated


Followup 2

Compose reply
Download message
From: Teng Liu <liu@mpe.mpg.de>
Date: Tue, 14 Aug 2018 15:43:29 +0200
Subject: Re: which CCF to use when running emldetect on multiple pointings (PR#83825)
To: Nora Loiseau <xmmhelp@sciops.esa.int>
--000000000000feebb405736566fe
Content-Type: text/plain; charset="UTF-8"

Dear Nora,

As you suggested, I run emosaic_prep and emosaicproc for one mosaic
observation 0677600101. In the output of emosaicproc, the CCF used by
emldetect are listed as:
emldetect:- CCF constituents accessed by the calibration server:
CifEntry{EMOS1, LINCOORD, 18, /xmm/ccf/public/EMOS1_LINCOORD_0018.CCF,
1998-01-01T00:00:00.000}
CifEntry{EMOS2, LINCOORD, 18, /xmm/ccf/public/EMOS2_LINCOORD_0018.CCF,
1998-01-01T00:00:00.000}
......

However, through these outputs, we can not tell which cif was used by
emldetect. In the case of running emldetect for non-mosaic different
observations, there are more than one different cif. It is never mentioned
anywhere which one should be used. Does it mean that emldetect does not
depend on cif and any one can be used?


Cheers,
Teng

On Mon, Aug 13, 2018 at 12:02 PM, Nora Loiseau <xmmhelp@sciops.esa.int>
wrote:

> Dear Teng,
>
> It is not clear looking at the code, but please check the log of the tasks
> performed and you will see that the proper ccf are applied.
>
> Best regards,
>
> Nora
>
>
> > Thank you for your reply. I checked the PERL source code of
emosaicproc,
> > which you suggested to use. I am not good at the PERL language. But
seems
> > the emosaicproc is not setting any cif before running emldetect, and
> > therefore likely the cif of the last pointing in the loop is used by
> > emldetect. Is it true?
> >
> > Best regards,
> > Teng Liu
> >
> > On Fri, Aug 10, 2018 at 7:48 PM, Nora Loiseau
<xmmhelp@sciops.esa.int>
> > wrote:
> >
> >> Dear Dr. Liu,
> >>
> >> For your purpose we could ask you to try the following thread
> >> https://www.cosmos.esa.int/web/xmm-newton/sas-thread-src-
> >> find-overlap-stepbystep
> >>
> >> This is designed for Mosaic observations but can be applied to any
set
> of
> >> observations, renaming the directory prep_mosaic_001 each time, as
> follows:
> >>
> >> 1) Assuming that you want to detect sources in Obs1 and Obs2,
first of
> all
> >> proceed to obtain filtered event list, ccf.cif and *SUM.SAS for
each
> >> observation.
> >>
> >> 2) From your Work directory run emosaic-prep for Obs2, this will
create
> the
> >> resulting files in the directory ./prep_mosaic_001.
> >>
> >> 3) Rename ./prop-mosaic001 to ./prop_mosaic_002
> >>
> >> 4) From your Work directory run emosaic-prep for Obs1, this will
create
> the
> >> resulting files in the directory ./prop_mosaic_001
> >>
> >> 5) Run emosaicproc in the directory Work
> >>
> >> emosaicproc \
> >>    pnevlist='prep_mosaic_001/PNevt_P001.ds
> prep_mosaic_002/PNevt_P002.ds \
> >>    mos1evlist='prep_mosaic_001/MOS1evt_P001.ds
> >> prep_mosaic_002/MOS1evt_P002.ds
> >> \
> >>    mos2evlist='prep_mosaic_001/MOS2evt_P001.ds
> >> prep_mosaic_002/MOS2evt_P002.ds'
> >>
> >> 6) follow the rest of the thread.
> >>
> >> Best regards,
> >>
> >> Nora
> >> ----
> >> Dr. Nora Loiseau
> >> XMM-Newton User Support Group
> >>
> >> This message is intended only for the recipient(s) named above. It
may
> >> contain proprietary information and/or
> >> protected content. Any unauthorised disclosure, use, retention or
> >> dissemination is prohibited. If you have received
> >> this e-mail in error, please notify the sender immediately. ESA
applies
> >> appropriate organisational measures to protect
> >> personal data, in case of data privacy queries, please contact the
ESA
> >> Data Protection Officer (dpo@esa.int).
> >>
> >>
> >>
> >
> > --000000000000bc06e605734c5105
> > Content-Type: text/html; charset="UTF-8"
> > Content-Transfer-Encoding: quoted-printable
> >
> > <div dir=3D"ltr">Dear Mr. Nora
Loiseau,<div><br></div><div>Thank you
> for yo=
> > ur reply. I checked the PERL source code of emosaicproc, which you
> suggeste=
> > d to use. I am not good at the PERL language. But seems the
emosaicproc
> is =
> > not setting any cif before running emldetect, and therefore likely the
> cif =
> > of the last pointing in the loop is used by emldetect. Is it
> true?</div><di=
> > v><br></div><div>Best
regards,</div><div>Teng Liu</div></div><div
> class=3D"=
> > gmail_extra"><br><div class=3D"gmail_quote">On Fri, Aug
10, 2018 at 7:48
> PM=
> > , Nora Loiseau <span 

Message of length 23061 truncated


Reply 3

Resend
From: Nora Loiseau <xmmhelp@sciops.esa.int>
To: liu@mpe.mpg.de
Subject: Re: which CCF to use when running emldetect on multiple pointings (PR#83825)
Date: Thu Aug 16 14:24:51 2018
Dear Teng,

For the mosaic observation the ccf to be used will be the same, as the
observations were performed together. For the mosaic the best is to treat the
different sub-observations as independent observations.

For instance for the source at RA=2h 29m 18s Dec=-5d 38' 16" you will find
3 observations:
0677600133
0677600134
0404964701

The first 2 belong to the same mosaic and will have the same ccf.

Best regards,

Nora

> 
> As you suggested, I run emosaic_prep and emosaicproc for one mosaic
> observation 0677600101. In the output of emosaicproc, the CCF used by
> emldetect are listed as:
> emldetect:- CCF constituents accessed by the calibration server:
> CifEntry{EMOS1, LINCOORD, 18, /xmm/ccf/public/EMOS1_LINCOORD_0018.CCF,
> 1998-01-01T00:00:00.000}
> CifEntry{EMOS2, LINCOORD, 18, /xmm/ccf/public/EMOS2_LINCOORD_0018.CCF,
> 1998-01-01T00:00:00.000}
> ......
> 
> However, through these outputs, we can not tell which cif was used by
> emldetect. In the case of running emldetect for non-mosaic different
> observations, there are more than one different cif. It is never mentioned
> anywhere which one should be used. Does it mean that emldetect does not
> depend on cif and any one can be used?
> 
> 
> Cheers,
> Teng
> 
> On Mon, Aug 13, 2018 at 12:02 PM, Nora Loiseau
<xmmhelp@sciops.esa.int>
> wrote:
> 
>> Dear Teng,
>>
>> It is not clear looking at the code, but please check the log of the
tasks
>> performed and you will see that the proper ccf are applied.
>>
>> Best regards,
>>
>> Nora
>>
>>
>> > Thank you for your reply. I checked the PERL source code of
emosaicproc,
>> > which you suggested to use. I am not good at the PERL language.
But seems
>> > the emosaicproc is not setting any cif before running emldetect,
and
>> > therefore likely the cif of the last pointing in the loop is used
by
>> > emldetect. Is it true?
>> >
>> > Best regards,
>> > Teng Liu
>> >
>> > On Fri, Aug 10, 2018 at 7:48 PM, Nora Loiseau
<xmmhelp@sciops.esa.int>
>> > wrote:
>> >
>> >> Dear Dr. Liu,
>> >>
>> >> For your purpose we could ask you to try the following thread
>> >> https://www.cosmos.esa.int/web/xmm-newton/sas-thread-src-
>> >> find-overlap-stepbystep
>> >>
>> >> This is designed for Mosaic observations but can be applied to
any set
>> of
>> >> observations, renaming the directory prep_mosaic_001 each
time, as
>> follows:
>> >>
>> >> 1) Assuming that you want to detect sources in Obs1 and Obs2,
first of
>> all
>> >> proceed to obtain filtered event list, ccf.cif and *SUM.SAS
for each
>> >> observation.
>> >>
>> >> 2) From your Work directory run emosaic-prep for Obs2, this
will create
>> the
>> >> resulting files in the directory ./prep_mosaic_001.
>> >>
>> >> 3) Rename ./prop-mosaic001 to ./prop_mosaic_002
>> >>
>> >> 4) From your Work directory run emosaic-prep for Obs1, this
will create
>> the
>> >> resulting files in the directory ./prop_mosaic_001
>> >>
>> >> 5) Run emosaicproc in the directory Work
>> >>
>> >> emosaicproc \
>> >>    pnevlist='prep_mosaic_001/PNevt_P001.ds
>> prep_mosaic_002/PNevt_P002.ds \
>> >>    mos1evlist='prep_mosaic_001/MOS1evt_P001.ds
>> >> prep_mosaic_002/MOS1evt_P002.ds
>> >> \
>> >>    mos2evlist='prep_mosaic_001/MOS2evt_P001.ds
>> >> prep_mosaic_002/MOS2evt_P002.ds'
>> >>
>> >> 6) follow the rest of the thread.
>> >>
>> >> Best regards,
>> >>
>> >> Nora
>> >> ----
>> >> Dr. Nora Loiseau
>> >> XMM-Newton User Support Group
>> >>
>> >> This message is intended only for the recipient(s) named
above. It may
>> >> contain proprietary information and/or
>> >> protected content. Any unauthorised disclosure, use, retention
or
>> >> dissemination is prohibited. If you have received
>> >> this e-mail in error, please notify the sender immediately.
ESA applies
>> >> appropriate organisational measures to protect
>> >> personal data, in case of data privacy queries, please contact
the ESA
>> >> Data Protection Officer (dpo@esa.int).
>> >>
>> >>
>> >>
>> >
>> > --000000000000bc

Message of length 24324 truncated


Followup 3

Compose reply
Download message
From: Teng Liu <liu@mpe.mpg.de>
Date: Fri, 17 Aug 2018 10:07:25 +0200
Subject: Re: which CCF to use when running emldetect on multiple pointings (PR#83825)
To: Maria Diaz Trigo <xmmhelp@sciops.esa.int>
--0000000000009b71b905739d0e4a
Content-Type: text/plain; charset="UTF-8"

Dear Nora,

Thanks for your reply. But my question is not about mosaic observations. I
know that mosaic observations have the same cif. My question is about
non-mosaic, different-epoc observations. Take the example of the 3
observations:
0677600133
0677600134
0404964701
The first two have the same cif. But the third observation has a different
one. Which cif should be used when running emldetect? A cif is requested by
emldetect, but there is no instruction about which one to used.

Best regards,
Teng


On Thu, Aug 16, 2018 at 4:24 PM Nora Loiseau <xmmhelp@sciops.esa.int>
wrote:

> Dear Teng,
>
> For the mosaic observation the ccf to be used will be the same, as the
> observations were performed together. For the mosaic the best is to treat
> the
> different sub-observations as independent observations.
>
> For instance for the source at RA=2h 29m 18s Dec=-5d 38' 16" you will find
> 3 observations:
> 0677600133
> 0677600134
> 0404964701
>
> The first 2 belong to the same mosaic and will have the same ccf.
>
> Best regards,
>
> Nora
>
> >
> > As you suggested, I run emosaic_prep and emosaicproc for one mosaic
> > observation 0677600101. In the output of emosaicproc, the CCF used by
> > emldetect are listed as:
> > emldetect:- CCF constituents accessed by the calibration server:
> > CifEntry{EMOS1, LINCOORD, 18, /xmm/ccf/public/EMOS1_LINCOORD_0018.CCF,
> > 1998-01-01T00:00:00.000}
> > CifEntry{EMOS2, LINCOORD, 18, /xmm/ccf/public/EMOS2_LINCOORD_0018.CCF,
> > 1998-01-01T00:00:00.000}
> > ......
> >
> > However, through these outputs, we can not tell which cif was used by
> > emldetect. In the case of running emldetect for non-mosaic different
> > observations, there are more than one different cif. It is never
> mentioned
> > anywhere which one should be used. Does it mean that emldetect does
not
> > depend on cif and any one can be used?
> >
> >
> > Cheers,
> > Teng
> >
> > On Mon, Aug 13, 2018 at 12:02 PM, Nora Loiseau
<xmmhelp@sciops.esa.int>
> > wrote:
> >
> >> Dear Teng,
> >>
> >> It is not clear looking at the code, but please check the log of
the
> tasks
> >> performed and you will see that the proper ccf are applied.
> >>
> >> Best regards,
> >>
> >> Nora
> >>
> >>
> >> > Thank you for your reply. I checked the PERL source code of
> emosaicproc,
> >> > which you suggested to use. I am not good at the PERL
language. But
> seems
> >> > the emosaicproc is not setting any cif before running
emldetect, and
> >> > therefore likely the cif of the last pointing in the loop is
used by
> >> > emldetect. Is it true?
> >> >
> >> > Best regards,
> >> > Teng Liu
> >> >
> >> > On Fri, Aug 10, 2018 at 7:48 PM, Nora Loiseau
<xmmhelp@sciops.esa.int
> >
> >> > wrote:
> >> >
> >> >> Dear Dr. Liu,
> >> >>
> >> >> For your purpose we could ask you to try the following
thread
> >> >> https://www.cosmos.esa.int/web/xmm-newton/sas-thread-src-
> >> >> find-overlap-stepbystep
> >> >>
> >> >> This is designed for Mosaic observations but can be
applied to any
> set
> >> of
> >> >> observations, renaming the directory prep_mosaic_001 each
time, as
> >> follows:
> >> >>
> >> >> 1) Assuming that you want to detect sources in Obs1 and
Obs2, first
> of
> >> all
> >> >> proceed to obtain filtered event list, ccf.cif and
*SUM.SAS for each
> >> >> observation.
> >> >>
> >> >> 2) From your Work directory run emosaic-prep for Obs2,
this will
> create
> >> the
> >> >> resulting files in the directory ./prep_mosaic_001.
> >> >>
> >> >> 3) Rename ./prop-mosaic001 to ./prop_mosaic_002
> >> >>
> >> >> 4) From your Work directory run emosaic-prep for Obs1,
this will
> create
> >> the
> >> >> resulting files in the directory ./prop_mosaic_001
> >> >>
> >> >> 5) Run emosaicproc in the directory Work
> >> >>
> >> >> emosaicproc \
> >> >>    pnevlist='prep_mosaic_001/PNevt_P001.ds
> >> prep_mosaic_002/PNevt_P002.ds \
> >> >>    mos1evlist='prep_mosaic_001/MOS1evt_P001.ds
> >> >> prep_mosaic_002/MOS1evt_P002.ds
> >> >> \
> >> >> 

Message of length 71186 truncated


Reply 4

Resend
From: Nora Loiseau <xmmhelp@sciops.esa.int>
To: liu@mpe.mpg.de
Subject: Re: which CCF to use when running emldetect on multiple pointings (PR#83825)
Date: Fri Aug 17 12:17:26 2018
Dear Teng,

I consulted the SAS developer and he said that the CCF used by emosaic prep and
proc should be the correct ones. If you want to check he suggests to run the
tasks with higher verbosity, i.e. 6 or 7, and you should be able to see in the
logs which CCFs were used.

Best regards,

Nora


> 
> Dear Nora,
> 
> Thanks for your reply. But my question is not about mosaic observations. I
> know that mosaic observations have the same cif. My question is about
> non-mosaic, different-epoc observations. Take the example of the 3
> observations:
> 0677600133
> 0677600134
> 0404964701
> The first two have the same cif. But the third observation has a different
> one. Which cif should be used when running emldetect? A cif is requested
by
> emldetect, but there is no instruction about which one to used.
> 
> Best regards,
> Teng
> 
> 
> On Thu, Aug 16, 2018 at 4:24 PM Nora Loiseau <xmmhelp@sciops.esa.int>
wrote:
> 
>> Dear Teng,
>>
>> For the mosaic observation the ccf to be used will be the same, as the
>> observations were performed together. For the mosaic the best is to
treat
>> the
>> different sub-observations as independent observations.
>>
>> For instance for the source at RA=2h 29m 18s Dec=-5d 38' 16" you will
find
>> 3 observations:
>> 0677600133
>> 0677600134
>> 0404964701
>>
>> The first 2 belong to the same mosaic and will have the same ccf.
>>
>> Best regards,
>>
>> Nora
>>
>> >
>> > As you suggested, I run emosaic_prep and emosaicproc for one
mosaic
>> > observation 0677600101. In the output of emosaicproc, the CCF used
by
>> > emldetect are listed as:
>> > emldetect:- CCF constituents accessed by the calibration server:
>> > CifEntry{EMOS1, LINCOORD, 18,
/xmm/ccf/public/EMOS1_LINCOORD_0018.CCF,
>> > 1998-01-01T00:00:00.000}
>> > CifEntry{EMOS2, LINCOORD, 18,
/xmm/ccf/public/EMOS2_LINCOORD_0018.CCF,
>> > 1998-01-01T00:00:00.000}
>> > ......
>> >
>> > However, through these outputs, we can not tell which cif was used
by
>> > emldetect. In the case of running emldetect for non-mosaic
different
>> > observations, there are more than one different cif. It is never
>> mentioned
>> > anywhere which one should be used. Does it mean that emldetect
does not
>> > depend on cif and any one can be used?
>> >
>> >
>> > Cheers,
>> > Teng
>> >
>> > On Mon, Aug 13, 2018 at 12:02 PM, Nora Loiseau
<xmmhelp@sciops.esa.int>
>> > wrote:
>> >
>> >> Dear Teng,
>> >>
>> >> It is not clear looking at the code, but please check the log
of the
>> tasks
>> >> performed and you will see that the proper ccf are applied.
>> >>
>> >> Best regards,
>> >>
>> >> Nora
>> >>
>> >>
>> >> > Thank you for your reply. I checked the PERL source code
of
>> emosaicproc,
>> >> > which you suggested to use. I am not good at the PERL
language. But
>> seems
>> >> > the emosaicproc is not setting any cif before running
emldetect, and
>> >> > therefore likely the cif of the last pointing in the loop
is used by
>> >> > emldetect. Is it true?
>> >> >
>> >> > Best regards,
>> >> > Teng Liu
>> >> >
>> >> > On Fri, Aug 10, 2018 at 7:48 PM, Nora Loiseau
<xmmhelp@sciops.esa.int
>> >
>> >> > wrote:
>> >> >
>> >> >> Dear Dr. Liu,
>> >> >>
>> >> >> For your purpose we could ask you to try the
following thread
>> >> >>
https://www.cosmos.esa.int/web/xmm-newton/sas-thread-src-
>> >> >> find-overlap-stepbystep
>> >> >>
>> >> >> This is designed for Mosaic observations but can be
applied to any
>> set
>> >> of
>> >> >> observations, renaming the directory prep_mosaic_001
each time, as
>> >> follows:
>> >> >>
>> >> >> 1) Assuming that you want to detect sources in Obs1
and Obs2, first
>> of
>> >> all
>> >> >> proceed to obtain filtered event list, ccf.cif and
*SUM.SAS for each
>> >> >> observation.
>> >> >>
>> >> >> 2) From your Work directory run emosaic-prep for
Obs2, this will
>> create
>> >> the
>>

Message of length 69860 truncated

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