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 esas/85666
Full headers

From: Ryan Le Roux <LRXRYA001@myuct.ac.za>
Subject: Re: Error with 'adapt' command, not reading file that does exist
Compose reply
Download message
Move To:
0 replies:
0 followups:

Private message: yes  no

Notes:

Notification:


From: Ryan Le Roux <LRXRYA001@myuct.ac.za>
To: Ignacio de la Calle <xmmhelp@sciops.esa.int>
Subject: Re: Error with 'adapt' command, not reading file that does exist
Date: Tue, 17 Sep 2019 09:16:58 +0000
--_000_VI1PR03MB4335F5BD0247286ED79FBD2EA88F0VI1PR03MB4335eurp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Ignacio,

This is great news, thank you!

I thought I may have made an error on my end.

It is good to know that the effective area drops, I was unaware of this.

Thanks for following it up and getting back to me.

Kind regards,
Ryan
________________________________
From: Ignacio de la Calle <xmmhelp@sciops.esa.int>
Sent: Tuesday, September 17, 2019 11:09 AM
To: Ryan Le Roux <LRXRYA001@myuct.ac.za>
Subject: Re: Error with 'adapt' command, not reading file that does exist (=
PR#85613)

Dear Ryan,

Sorry for the delay. I just got a reply from the developer.

You are right, this is a bug in the code that needs to be solved. The fix w=
ill
take some time and will be released in a patch.

In the meantime, going up to 12keV is probably not worth it anyhow. The
effective area of
XMM drops fast beyond 10keV. For now you could just use 9999 in your call. =
I
know its not
ideal but you could at least look at the output and asses what you get.

Regards,

Ignacio de la Calle
XMM-Newton SOC

> --_000_VI1PR03MB43359B553C55D17F7034EBE2A8B70VI1PR03MB4335eurp_
> Content-Type: text/plain; charset=3D"us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
> Hi Ignacio,
>
> Thank you very much for getting back to me and passing it on.
>
> Kind regards,
> Ryan
> ________________________________
> From: Ignacio de la Calle <xmmhelp@sciops.esa.int>
> Sent: Monday, September 9, 2019 4:40 PM
> To: Ryan Le Roux <LRXRYA001@myuct.ac.za>
> Subject: Re: Error with 'adapt' command, not reading file that does exist=
 (=3D
> PR#85578)
>
> Dear Ryan,
>
> I need to pass this to the ESAS developers. I will come back to you when =
I =3D
> have
> an answer.
>
> Thanks,
>
> Ignacio de la Calle
> XMM-Newton SOC
>
>> Submission from: (NULL) (193.147.152.102)
>>
>>
>> Hi there,
>>
>> I am busy producing background subtracted images (using thread
>> https://www.cosmos.esa.int/web/xmm-newton/sas-thread-esasimage, and
data
> OBSID
>> 0674110101, 0674110201 and 0674110401), and keep running into an error
w=
i=3D
> th
> the
>> 'adapt' command (at step 14).
>>
>> I am attempting to make an image in the 2.5-12 keV range (successfully
m=
a=3D
> de
>> 0.3-1.5 keV and 1.5-2.5 keV), but when I try run the adapt command as
> follows:
>> adapt smoothingcounts=3D3D50 thresholdmasking=3D3D0.02 detector=3D3D0
bi=
nning=3D
> =3D3D2 elow=3D3D2500
>> ehigh=3D3D12000 withmaskcontrol=3D3Dno withpartcontrol=3D3Dyes
withsoftc=
ontrol=3D
> =3D3Dyes
>> withswcxcontrol=3D3D0
>>
>> I get the error:
>> adapt:-  ADAPT: Retrieving image: comb-obj-im-2500-****.fits
>> adapt:-  ADAPT 01a: STATUS=3D3D         104  on return from retfit
>> ** adapt: error (noRet), Error reading image
>>
>> Which is strange, since the file "comb-obj-im-2500-12000.fits" file
does
> exist,
>> it appears that the code is not able to handle more than 4 digits for
th=
e
> second
>> eV value? When looking up any similar errors from other users, it was a
=
c=3D
> ase
> of
>> a file missing. I'm somewhat new to XMM and could be making an error
> somewhere,
>> but since I have been able to make 2 other images in the aforementioned
=
b=3D
> ands
>> for all three datasets, makes me suspicious that it's related to the
upp=
e=3D
> r
>> energy level I have chosen.
>>
>> Thanks in advance!
>>
>> Kind regards,
>> Ryan
>>
>>
>
> 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).
>
>
> Disclaimer - University of Cape Town This email is subject to UCT policie=
s =3D
> and email disclaimer published on our website at http://www.uct.ac.za/mai=
n/=3D
> email-disclaimer or obtainable from +27 21 650 9111. If this email is not=
 r=3D
> elated to the business of UCT, it is sent by the sender in an individual =
ca=3D
> pacity. Please report security incidents or abuse via https://csirt.uct.a=
c.=3D
> za/page/report-an-incident.php.
>
> --_000_VI1PR03MB43359B553C55D17F7034EBE2A8B70VI1PR03MB4335eurp_
> Content-Type: text/html; charset=3D"us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
> <html>
> &l

Message of length 32663 truncated
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