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 SASv16.1/82879
Full headers

From: alex@mpa-garching.mpg.de
Subject: Pixel-Unit of psfgen output image
Compose reply
Download message
Move To:
1 replies: 1
1 followups: 1

Private message: yes  no

Notes:

Notification:


Date: Fri, 19 Jan 2018 21:07:46 GMT
From: alex@mpa-garching.mpg.de
To: xmmhelp@sciops.esa.int
CC: alex@mpa-garching.mpg.de
Subject: Pixel-Unit of psfgen output image
Full_Name: Alex Kolodzig
Submission from: (NULL) (130.183.89.170)


Dear Helpdesk

What is the pixel-unit of the psfgen output image?

Example command:
psfgen image=Image_Binned.fits useodf=no region='(X,Y) IN box( 27418.28,
27084.62, 4800, 4800 )' instrument=M1 ccdnr=1 node=PRIMARY
cammode=PrimeFullWindow filter=Open ccdtemp=120 camtemp=120 temptrack=yes
starttime=1999-12-10T14:32:00.000 duration=0 level=ELLBETA parameter=0
random=yes binning=0 ccf='' ccflog=no energy=1000 weight=1 theta=-1 phi=-1
rotate=-1 coortype='' xsize=0 ysize=0 output=output.fits  -w 1 -V 4


I tried as an input-image several images with different pixel-binning (e.g.
[1,2,4] arcsec/pixel, created with evselect) but the corresponding output-images
remain identical. So to me it appears that the image-pixel-binning from the
input-image are not adopted at all.

Further, if I don't specify xsize & ysize and use as region a box-size (see
example) of 4800 x 4800 [sky-pixels] (4 x 4 [arcmin]), I get an
output-image-dimension of 437x437 [img-pixels] and that's independent of the
detector (and image-pixel-binning) of the input-image. The image-size increases
linearly with the box-size but it is not clear to me how 4800 sky-pixels and 437
img-pixels correlate.

If 4800 sky-pixels corresponds to 437 img-pixels then I get ~0.55
arcmin/img-pixels. Is that suppose to be like that? I couldn't find anything
about this in the SAS documentation.

Even stranger is that 437 * 1.1 arcsec = ~8 arcmin, where 1.1 arcsec is the
CCD-pixel-size of MOS. So, I though that the pixel-unit is given in CCD-pixels
and my output-image is just twice the size of my box-size. However, why do I get
the same output-image-dimensions for PN was well, where the CCD-pixel-size is
4.1 arcsec ?

Thanks a lot in advance for your help

I'm using:
SAS release: xmmsas_20170719_1539-16.1.0 (sasversion-1.2)
Compiled on: Fri Jul 28 01:07:14 CEST 2017
Compiled by: sasbuild@sasbld01n.net4.lan
Platform   : RHEL6.8 64


Best wishes
Alex


Reply 1

Resend
From: Jacobo Ebrero <xmmhelp@sciops.esa.int>
To: alex@mpa-garching.mpg.de
Subject: Re: Pixel-Unit of psfgen output image (PR#82879)
Date: Mon Jan 22 10:50:58 2018
Dear Alex,

After consulting with the task developer, he confirms that the output pixel size
is always 1x1 arsec (20x20 DET pixels).

You can make the image bigger using the xsize, ysize parameters but the pixel
resolution remains the same. You may use fimgbin to rebin it if necessary.

Best regards,
Jacobo
----------------------
Dr. Jacobo Ebrero
XMM-Newton SOC
User Support Group


Followup 1

Compose reply
Download message
Date: Mon, 22 Jan 2018 14:46:48 +0100
From: alex_kolo <alex_kolo@gmx.de>
To: "Jacobo Ebrero" <xmmhelp@sciops.esa.int>
Subject: Re: Pixel-Unit of psfgen output image (PR#82879)
Dear Jacobo

Thank you for the quick and helpful answer. That solves my problems.

For future reference, I think it would be useful to included this information in
the SAS documentation.

Best regards, 
Alex


 ---- On Mon, 22 Jan 2018 11:50:57 +0100 Jacobo Ebrero
<xmmhelp@sciops.esa.int> wrote ---- 
 > Dear Alex, 
 >  
 > After consulting with the task developer, he confirms that the output
pixel size 
 > is always 1x1 arsec (20x20 DET pixels). 
 >  
 > You can make the image bigger using the xsize, ysize parameters but the
pixel 
 > resolution remains the same. You may use fimgbin to rebin it if necessary.

 >  
 > Best regards, 
 > Jacobo 
 > ---------------------- 
 > Dr. Jacobo Ebrero 
 > XMM-Newton SOC 
 > User Support Group 
 >  
 > This message and any attachments are intended for the use of the addressee
or addressees only. 
 > The unauthorised disclosure, use, dissemination or copying (either in
whole or in part) of its 
 > content is not permitted. 
 > If you received this message in error, please notify the sender and delete
it from your system. 
 > Emails can be altered and their integrity cannot be guaranteed by the
sender. 
 >  
 > Please consider the environment before printing this email. 
 >  
 >  
 > 



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