<![CDATA[AstrOmatic forum - All Forums]]> http://www.astromatic.net/forum/ Sat, 04 Feb 2012 10:01:02 +0000 MyBB <![CDATA[Model Images for EyE]]> http://www.astromatic.net/forum/showthread.php?tid=763 Thu, 05 Jan 2012 01:09:52 +0000 http://www.astromatic.net/forum/showthread.php?tid=763
I have been developing a way to use EyE to enhance the way we are currently using SExtractor to find objects in our fields. (The general use of it I guess). At the moment I have not had very much success with getting the EyE to recognise what is in the model images. The patterns it picks out don't seem to have any correlation to the image at all. i.e. A model image may have 2 or 3 gaussians on it but EyE will pick out over 100 patterns. Have I misunderstood what the patterns are? Has anyone come across this before? I know that there must be something with the model images but I am unsure as to how they are so wrong….

Any insight would be very much appreciated!

Cheers,
Elise]]>
I have been developing a way to use EyE to enhance the way we are currently using SExtractor to find objects in our fields. (The general use of it I guess). At the moment I have not had very much success with getting the EyE to recognise what is in the model images. The patterns it picks out don't seem to have any correlation to the image at all. i.e. A model image may have 2 or 3 gaussians on it but EyE will pick out over 100 patterns. Have I misunderstood what the patterns are? Has anyone come across this before? I know that there must be something with the model images but I am unsure as to how they are so wrong….

Any insight would be very much appreciated!

Cheers,
Elise]]> <![CDATA[Bug in coadd.c when COMBINE_BUFSIZE > 2 GB ?]]> http://www.astromatic.net/forum/showthread.php?tid=762 Wed, 04 Jan 2012 02:13:47 +0000 http://www.astromatic.net/forum/showthread.php?tid=762
In coadd.c, line ~323:
Code:
nbuflinesmax = (prefs.coaddbuf_size * 1024 * 1024)
    / (2*(multiwidth+outwidth)*sizeof(PIXTYPE));

If prefs.coaddbuf_size is > 2048, this statement overflows 4 byte integers, leading to unexpected results for nbuflinesmax. This bug can then manifest itself in the call a few lines later:

Code:
QMALLOC(multibuf, PIXTYPE, nbuflinesmax*multiwidth);

which raises the error:
> Not enough memory for multibuf (nbuflinesmax * multiwidth elements) !

Two side notes:

First, it would be nice if the above error raised by QMALLOC (in define.h) reported the actual number of elements (and/or bytes) it is trying to allocate, in addition to the names of the variables.

Second (and I may be misunderstanding exactly what the code is doing here) if the user sets prefs.coaddbuf_size way higher than it needs to be (how I ran into this problem), would it make sense to only allocate the space needed (e.g., total size of all images) rather than the entire value of prefs.coaddbuf_size?]]>
In coadd.c, line ~323:
Code:
nbuflinesmax = (prefs.coaddbuf_size * 1024 * 1024)
    / (2*(multiwidth+outwidth)*sizeof(PIXTYPE));

If prefs.coaddbuf_size is > 2048, this statement overflows 4 byte integers, leading to unexpected results for nbuflinesmax. This bug can then manifest itself in the call a few lines later:

Code:
QMALLOC(multibuf, PIXTYPE, nbuflinesmax*multiwidth);

which raises the error:
> Not enough memory for multibuf (nbuflinesmax * multiwidth elements) !

Two side notes:

First, it would be nice if the above error raised by QMALLOC (in define.h) reported the actual number of elements (and/or bytes) it is trying to allocate, in addition to the names of the variables.

Second (and I may be misunderstanding exactly what the code is doing here) if the user sets prefs.coaddbuf_size way higher than it needs to be (how I ran into this problem), would it make sense to only allocate the space needed (e.g., total size of all images) rather than the entire value of prefs.coaddbuf_size?]]> <![CDATA[Patch for SCAMP to build with PLPLOT-5.9.9]]> http://www.astromatic.net/forum/showthread.php?tid=761 Sun, 01 Jan 2012 21:58:10 +0000 http://www.astromatic.net/forum/showthread.php?tid=761
it's been a long time since my last post, since I'm not working in astronomy anymore. But as I'm still interested in the field and now working as a developer, I'll post a patch to make SAMP compile with recent versions of PLPLOT.

The easiest way to get things done would be to define PL_DEPRECATED in the source, but since we want to be compatible in the future, some changes need to me made...

See https://bugs.gentoo.org/show_bug.cgi?id=396723 (I'll attach the patch here, as well.)

BTW: Please delete the profile with the username "jankoh" which I created just an hour ago. I can provide Mail-Adresses and stuff via PN, if that is needed to confirm that both profiles have the same person in front of the keyboard. Smile
Here's the patch...

.txt  scamp-1.7.0-r2.txt (Size: 24.36 KB / Downloads: 10) ]]>
it's been a long time since my last post, since I'm not working in astronomy anymore. But as I'm still interested in the field and now working as a developer, I'll post a patch to make SAMP compile with recent versions of PLPLOT.

The easiest way to get things done would be to define PL_DEPRECATED in the source, but since we want to be compatible in the future, some changes need to me made...

See https://bugs.gentoo.org/show_bug.cgi?id=396723 (I'll attach the patch here, as well.)

BTW: Please delete the profile with the username "jankoh" which I created just an hour ago. I can provide Mail-Adresses and stuff via PN, if that is needed to confirm that both profiles have the same person in front of the keyboard. Smile
Here's the patch...

.txt  scamp-1.7.0-r2.txt (Size: 24.36 KB / Downloads: 10) ]]> <![CDATA[bad coadd.fits from SDSS mosaic ]]> http://www.astromatic.net/forum/showthread.php?tid=760 Fri, 30 Dec 2011 18:17:22 +0000 http://www.astromatic.net/forum/showthread.php?tid=760 I'm a bit of a newbie so I'm sorry if this is just because of something I missed. I'm trying to resample and combine sets of SDSS images which fall with in a particular radius of a source. As a result I'm working with images from different runs and taken with different ccds. I'm using 2.19.1 compiled (from source code) on Ubuntu Oneiric 11.10 and can't seem to get things working properly. (I haven't quite figured out how to get the RPM installed, sadly enough).

Initially I tried to resample and combine the images (I'm working with 5 or so) in one run, but no mater how I fiddled with the configuration file I could only get at best a final coadd.fits with all zeros (once I managed to get a single pixel with a 10^6 value, but that was a bit of a fluke). I then tried to just combine them without resampling and managed to get a somewhat mutilated version of the mosaic I was looking for (see attached image, should be only one galaxy). I thought that it might have something to do with this particular set of images, but I got the same result with an entirely different set as well.

I poked around here and found some interesting leads (like this one re: combining images with different CTYPEs
) but I haven't been able to turn up anything that works. I'd really appreciate any help with this, and again I'm sorry if this is mostly stupidity on my part.
Thanks,
CT

.jpg  coadd.jpg (Size: 16.96 KB / Downloads: 13) ]]> I'm a bit of a newbie so I'm sorry if this is just because of something I missed. I'm trying to resample and combine sets of SDSS images which fall with in a particular radius of a source. As a result I'm working with images from different runs and taken with different ccds. I'm using 2.19.1 compiled (from source code) on Ubuntu Oneiric 11.10 and can't seem to get things working properly. (I haven't quite figured out how to get the RPM installed, sadly enough).

Initially I tried to resample and combine the images (I'm working with 5 or so) in one run, but no mater how I fiddled with the configuration file I could only get at best a final coadd.fits with all zeros (once I managed to get a single pixel with a 10^6 value, but that was a bit of a fluke). I then tried to just combine them without resampling and managed to get a somewhat mutilated version of the mosaic I was looking for (see attached image, should be only one galaxy). I thought that it might have something to do with this particular set of images, but I got the same result with an entirely different set as well.

I poked around here and found some interesting leads (like this one re: combining images with different CTYPEs
) but I haven't been able to turn up anything that works. I'd really appreciate any help with this, and again I'm sorry if this is mostly stupidity on my part.
Thanks,
CT

.jpg  coadd.jpg (Size: 16.96 KB / Downloads: 13) ]]> <![CDATA[help with HAWKI astrometry]]> http://www.astromatic.net/forum/showthread.php?tid=759 Tue, 27 Dec 2011 22:45:00 +0000 http://www.astromatic.net/forum/showthread.php?tid=759
I write again with a problem in connection with the astrometry of ESO's HAWKI IR camera. I have tried hard to solve the astrometry, and succeeded in some instances, but there are cases which I cannot solve. I attach one such example - for a single chip. There are lots of stars in the field, yet scamp does not find the solution. Your help would be greatly appreciated, for instance by checking the setup files for astromatic.

I have placed all relevant files in a tar ball, which contains the HAWKI chip image and a weight map, as well as a README file indicating the sequence of commands I run. This tar ball is available here:

http://www.das.uchile.cl/~simon/ftp/help.tgz

it is about 15MB and expands into ./help_astromatic

Many thanks,

Simon Casassus.]]>
I write again with a problem in connection with the astrometry of ESO's HAWKI IR camera. I have tried hard to solve the astrometry, and succeeded in some instances, but there are cases which I cannot solve. I attach one such example - for a single chip. There are lots of stars in the field, yet scamp does not find the solution. Your help would be greatly appreciated, for instance by checking the setup files for astromatic.

I have placed all relevant files in a tar ball, which contains the HAWKI chip image and a weight map, as well as a README file indicating the sequence of commands I run. This tar ball is available here:

http://www.das.uchile.cl/~simon/ftp/help.tgz

it is about 15MB and expands into ./help_astromatic

Many thanks,

Simon Casassus.]]> <![CDATA[output files from swarp]]> http://www.astromatic.net/forum/showthread.php?tid=758 Sat, 24 Dec 2011 11:04:02 +0000 http://www.astromatic.net/forum/showthread.php?tid=758
I have a question about output files of SWARP.
I need to have all aligned images separately (before they are combined). Can I have these images too? How can I change the output files?

Best Regareds
Sedighe Sajadian]]>
I have a question about output files of SWARP.
I need to have all aligned images separately (before they are combined). Can I have these images too? How can I change the output files?

Best Regareds
Sedighe Sajadian]]> <![CDATA[Error: Not enough memory for set->sample]]> http://www.astromatic.net/forum/showthread.php?tid=756 Wed, 21 Dec 2011 16:28:23 +0000 http://www.astromatic.net/forum/showthread.php?tid=756
I'm trying to run SCAMP on 16 ACS images, and I'm hitting a memory error. I've changed the limits as mentioned in the manual:
>limit
cputime unlimited
filesize unlimited
datasize unlimited
stacksize unlimited
coredumpsize 0 kbytes
memoryuse unlimited
vmemoryuse unlimited
descriptors 1024
memorylocked 64 kbytes
maxproc 26058

But when I run scamp I get the following error:
> Catalog USNO-B1.0 (Bj band) : Object #25090000 / 25090000 samples stored
> Not enough memory for set->sample (nsample elements) !


The full output is:
scamp *circ.cat

> WARNING: scamp.conf not found, using internal defaults

----- SCAMP 1.7.0 started on 2011-12-21 at 11:20:36 with 4 threads

----- 16 inputs:
j8pi07b3q_circ.cat: "no ident " no ext. header 1 set 1066 detections
j8pi07bfq_circ.cat: "no ident " no ext. header 1 set 1084 detections
j8pi07bjq_circ.cat: "no ident " no ext. header 1 set 1059 detections
j8pi07c3q_circ.cat: "no ident " no ext. header 1 set 1111 detections
j8pi08a8q_circ.cat: "no ident " no ext. header 1 set 1182 detections
j8pi08adq_circ.cat: "no ident " no ext. header 1 set 1197 detections
j8pi08asq_circ.cat: "no ident " no ext. header 1 set 1203 detections
j8pi08zyq_circ.cat: "no ident " no ext. header 1 set 1085 detections
j8pi09osq_circ.cat: "no ident " no ext. header 1 set 1169 detections
j8pi09ozq_circ.cat: "no ident " no ext. header 1 set 906 detections
j8pi09p5q_circ.cat: "no ident " no ext. header 1 set 1229 detections
j8pi09pfq_circ.cat: "no ident " no ext. header 1 set 1152 detections
j8pi10nbq_circ.cat: "no ident " no ext. header 1 set 917 detections
j8pi10neq_circ.cat: "no ident " no ext. header 1 set 1153 detections
j8pi10niq_circ.cat: "no ident " no ext. header 1 set 1066 detections
j8pi10nmq_circ.cat: "no ident " no ext. header 1 set 1200 detections

----- 17779 detections loaded

----- 1 instrument found for astrometry:

Instrument A1 :
FILTER = 'F775W '
QRUNID =

----- 1 instrument found for photometry:

Instrument P1 :
FILTER = 'F775W '

----- 1 field group found:

Group 1: 16 fields at 02:16:33.43 -17:47:51.6 with radius 3.43'
instruments center coordinates radius scale
j8pi07b3q_circ.cat A1 P1 02:16:35.62 -17:47:05.6 2.491' 0.05000"
j8pi07bfq_circ.cat A1 P1 02:16:35.62 -17:47:05.7 2.491' 0.05000"
j8pi07bjq_circ.cat A1 P1 02:16:35.50 -17:47:08.1 2.491' 0.05000"
j8pi07c3q_circ.cat A1 P1 02:16:35.51 -17:47:08.2 2.491' 0.05000"
j8pi08a8q_circ.cat A1 P1 02:16:35.63 -17:47:06.0 2.491' 0.05000"
j8pi08adq_circ.cat A1 P1 02:16:35.52 -17:47:08.3 2.491' 0.05000"
j8pi08asq_circ.cat A1 P1 02:16:35.52 -17:47:08.5 2.491' 0.05000"
j8pi08zyq_circ.cat A1 P1 02:16:35.63 -17:47:05.8 2.491' 0.05000"
j8pi09osq_circ.cat A1 P1 02:16:31.40 -17:48:37.6 2.491' 0.05000"
j8pi09ozq_circ.cat A1 P1 02:16:31.39 -17:48:37.7 2.491' 0.05000"
j8pi09p5q_circ.cat A1 P1 02:16:31.19 -17:48:37.8 2.491' 0.05000"
j8pi09pfq_circ.cat A1 P1 02:16:31.18 -17:48:37.9 2.491' 0.05000"
j8pi10nbq_circ.cat A1 P1 02:16:31.20 -17:48:35.4 2.491' 0.05000"
j8pi10neq_circ.cat A1 P1 02:16:31.21 -17:48:35.3 2.491' 0.05000"
j8pi10niq_circ.cat A1 P1 02:16:31.38 -17:48:33.8 2.491' 0.05000"
j8pi10nmq_circ.cat A1 P1 02:16:31.38 -17:48:33.7 2.491' 0.05000"

----- Reference catalogs:

> Catalog USNO-B1.0 (Bj band) : Object #25090000 / 25090000 samples stored
> Not enough memory for set->sample (nsample elements) !

Help?

Thanks,
ReiCow]]>
I'm trying to run SCAMP on 16 ACS images, and I'm hitting a memory error. I've changed the limits as mentioned in the manual:
>limit
cputime unlimited
filesize unlimited
datasize unlimited
stacksize unlimited
coredumpsize 0 kbytes
memoryuse unlimited
vmemoryuse unlimited
descriptors 1024
memorylocked 64 kbytes
maxproc 26058

But when I run scamp I get the following error:
> Catalog USNO-B1.0 (Bj band) : Object #25090000 / 25090000 samples stored
> Not enough memory for set->sample (nsample elements) !


The full output is:
scamp *circ.cat

> WARNING: scamp.conf not found, using internal defaults

----- SCAMP 1.7.0 started on 2011-12-21 at 11:20:36 with 4 threads

----- 16 inputs:
j8pi07b3q_circ.cat: "no ident " no ext. header 1 set 1066 detections
j8pi07bfq_circ.cat: "no ident " no ext. header 1 set 1084 detections
j8pi07bjq_circ.cat: "no ident " no ext. header 1 set 1059 detections
j8pi07c3q_circ.cat: "no ident " no ext. header 1 set 1111 detections
j8pi08a8q_circ.cat: "no ident " no ext. header 1 set 1182 detections
j8pi08adq_circ.cat: "no ident " no ext. header 1 set 1197 detections
j8pi08asq_circ.cat: "no ident " no ext. header 1 set 1203 detections
j8pi08zyq_circ.cat: "no ident " no ext. header 1 set 1085 detections
j8pi09osq_circ.cat: "no ident " no ext. header 1 set 1169 detections
j8pi09ozq_circ.cat: "no ident " no ext. header 1 set 906 detections
j8pi09p5q_circ.cat: "no ident " no ext. header 1 set 1229 detections
j8pi09pfq_circ.cat: "no ident " no ext. header 1 set 1152 detections
j8pi10nbq_circ.cat: "no ident " no ext. header 1 set 917 detections
j8pi10neq_circ.cat: "no ident " no ext. header 1 set 1153 detections
j8pi10niq_circ.cat: "no ident " no ext. header 1 set 1066 detections
j8pi10nmq_circ.cat: "no ident " no ext. header 1 set 1200 detections

----- 17779 detections loaded

----- 1 instrument found for astrometry:

Instrument A1 :
FILTER = 'F775W '
QRUNID =

----- 1 instrument found for photometry:

Instrument P1 :
FILTER = 'F775W '

----- 1 field group found:

Group 1: 16 fields at 02:16:33.43 -17:47:51.6 with radius 3.43'
instruments center coordinates radius scale
j8pi07b3q_circ.cat A1 P1 02:16:35.62 -17:47:05.6 2.491' 0.05000"
j8pi07bfq_circ.cat A1 P1 02:16:35.62 -17:47:05.7 2.491' 0.05000"
j8pi07bjq_circ.cat A1 P1 02:16:35.50 -17:47:08.1 2.491' 0.05000"
j8pi07c3q_circ.cat A1 P1 02:16:35.51 -17:47:08.2 2.491' 0.05000"
j8pi08a8q_circ.cat A1 P1 02:16:35.63 -17:47:06.0 2.491' 0.05000"
j8pi08adq_circ.cat A1 P1 02:16:35.52 -17:47:08.3 2.491' 0.05000"
j8pi08asq_circ.cat A1 P1 02:16:35.52 -17:47:08.5 2.491' 0.05000"
j8pi08zyq_circ.cat A1 P1 02:16:35.63 -17:47:05.8 2.491' 0.05000"
j8pi09osq_circ.cat A1 P1 02:16:31.40 -17:48:37.6 2.491' 0.05000"
j8pi09ozq_circ.cat A1 P1 02:16:31.39 -17:48:37.7 2.491' 0.05000"
j8pi09p5q_circ.cat A1 P1 02:16:31.19 -17:48:37.8 2.491' 0.05000"
j8pi09pfq_circ.cat A1 P1 02:16:31.18 -17:48:37.9 2.491' 0.05000"
j8pi10nbq_circ.cat A1 P1 02:16:31.20 -17:48:35.4 2.491' 0.05000"
j8pi10neq_circ.cat A1 P1 02:16:31.21 -17:48:35.3 2.491' 0.05000"
j8pi10niq_circ.cat A1 P1 02:16:31.38 -17:48:33.8 2.491' 0.05000"
j8pi10nmq_circ.cat A1 P1 02:16:31.38 -17:48:33.7 2.491' 0.05000"

----- Reference catalogs:

> Catalog USNO-B1.0 (Bj band) : Object #25090000 / 25090000 samples stored
> Not enough memory for set->sample (nsample elements) !

Help?

Thanks,
ReiCow]]> <![CDATA[installing on cygwin]]> http://www.astromatic.net/forum/showthread.php?tid=755 Wed, 14 Dec 2011 21:03:28 +0000 http://www.astromatic.net/forum/showthread.php?tid=755
I have looked through the forums and did not find an answer to my question. I am trying to install Sextractor on cygwin to do a quick and dirty port to windows. I continually get the following error:

Code:
checking clapack.h usability... no
checking clapack.h presence... yes
configure: WARNING: clapack.h: present but cannot be compiled
configure: WARNING: clapack.h:     check for missing prerequisite headers?
configure: WARNING: clapack.h: see the Autoconf documentation
configure: WARNING: clapack.h:     section "Present But Cannot Be Compiled"
configure: WARNING: clapack.h: proceeding with the compiler's result
configure: WARNING:     ## ---------------------------- ##
configure: WARNING:     ## Report this to bertin@iap.fr ##
configure: WARNING:     ## ---------------------------- ##
checking for clapack.h... no
checking for clapack_dpotrf in -llapack... no
checking for cblas_dgemm in -lcblas... no
checking for clapack_dpotrf in -llapack... no
checking for cblas_dgemm in -lcblas... no
configure: error: CBLAS/LAPack library files not found in ~/ATLAS/AtlasInst/lib/! Exiting.

I have compiled ATLAS and CLAPACK and to the best of my knowledge linked them in correctly, but I am obviously missing something. Can anyone help? Thanks a bunch!]]>
I have looked through the forums and did not find an answer to my question. I am trying to install Sextractor on cygwin to do a quick and dirty port to windows. I continually get the following error:

Code:
checking clapack.h usability... no
checking clapack.h presence... yes
configure: WARNING: clapack.h: present but cannot be compiled
configure: WARNING: clapack.h:     check for missing prerequisite headers?
configure: WARNING: clapack.h: see the Autoconf documentation
configure: WARNING: clapack.h:     section "Present But Cannot Be Compiled"
configure: WARNING: clapack.h: proceeding with the compiler's result
configure: WARNING:     ## ---------------------------- ##
configure: WARNING:     ## Report this to bertin@iap.fr ##
configure: WARNING:     ## ---------------------------- ##
checking for clapack.h... no
checking for clapack_dpotrf in -llapack... no
checking for cblas_dgemm in -lcblas... no
checking for clapack_dpotrf in -llapack... no
checking for cblas_dgemm in -lcblas... no
configure: error: CBLAS/LAPack library files not found in ~/ATLAS/AtlasInst/lib/! Exiting.

I have compiled ATLAS and CLAPACK and to the best of my knowledge linked them in correctly, but I am obviously missing something. Can anyone help? Thanks a bunch!]]> <![CDATA[Multithreading shows no effect?]]> http://www.astromatic.net/forum/showthread.php?tid=754 Sun, 11 Dec 2011 18:36:57 +0000 http://www.astromatic.net/forum/showthread.php?tid=754
I wanted to install sextractor v2.8.6 to see the effect of multi-threading (which apparently is not yet activated for 2.5.0, even though the NTHREADS keyword is there). I ran into the same problem as many other folks here, failing to make the configure script recognise my ATLAS installation (i'm using ubuntu 11.10).
I tried the --without-atlas option, but the configure script would still look for it. Same with --disable-model-fitting. The latest repository version (2.14.7) recognised the latter option though, and Sextractor compiled fine.

However, I don't see any effect setting NTHREADS to a value larger than 1.

Can it be that multi-threading is used for model-fitting only, but not for the detection process? I'm only interested in creating source catalogs from single-extension FITS files.

Thanks,

mischa]]>
I wanted to install sextractor v2.8.6 to see the effect of multi-threading (which apparently is not yet activated for 2.5.0, even though the NTHREADS keyword is there). I ran into the same problem as many other folks here, failing to make the configure script recognise my ATLAS installation (i'm using ubuntu 11.10).
I tried the --without-atlas option, but the configure script would still look for it. Same with --disable-model-fitting. The latest repository version (2.14.7) recognised the latter option though, and Sextractor compiled fine.

However, I don't see any effect setting NTHREADS to a value larger than 1.

Can it be that multi-threading is used for model-fitting only, but not for the detection process? I'm only interested in creating source catalogs from single-extension FITS files.

Thanks,

mischa]]> <![CDATA[Scamp detects false groups]]> http://www.astromatic.net/forum/showthread.php?tid=752 Thu, 01 Dec 2011 17:17:09 +0000 http://www.astromatic.net/forum/showthread.php?tid=752

I sometimes get a message:
> WARNING: FK4 precession formulae not yet implemented:
Astrometry may be slightly inaccurate

sometimes it does not detect any fields and returns:
> *Error*: CDELT parameters out of range

sometimes it will correctly detect 1 group of 45 fields, sometimes 2 or more.

Here is an example of one output for one invocation of scamp:
Group 3: 1 field at 21:27:21.08 +08:37:13.4 with radius 4671'
instruments center coordinates radius scale
lfsr_1178_04_mef.fits A1 P1 21:27:21.08 +08:37:13.4 4671.' 0.1591"


on the next invocation of scamp, nothing has changed but now it claims:
Group 4: 1 field at 19:09:57.64 +14:28:37.6 with radius 4531'
instruments center coordinates radius scale
lfsr_1178_04_mef.fits A1 P1 19:09:57.64 +14:28:37.6 4531.' 0.1591"


I am guessing a header parameter is wrong but the problem isn't repeatable. Sometimes it works.

I am running scamp v.1.7.0 on a Mac server v.10.5.8, the fits_ldac file is attached. Thanks and cheers, Andy

.fits  lfsr_1178_04_mef.fits (Size: 570.94 KB / Downloads: 10) ]]>

I sometimes get a message:
> WARNING: FK4 precession formulae not yet implemented:
Astrometry may be slightly inaccurate

sometimes it does not detect any fields and returns:
> *Error*: CDELT parameters out of range

sometimes it will correctly detect 1 group of 45 fields, sometimes 2 or more.

Here is an example of one output for one invocation of scamp:
Group 3: 1 field at 21:27:21.08 +08:37:13.4 with radius 4671'
instruments center coordinates radius scale
lfsr_1178_04_mef.fits A1 P1 21:27:21.08 +08:37:13.4 4671.' 0.1591"


on the next invocation of scamp, nothing has changed but now it claims:
Group 4: 1 field at 19:09:57.64 +14:28:37.6 with radius 4531'
instruments center coordinates radius scale
lfsr_1178_04_mef.fits A1 P1 19:09:57.64 +14:28:37.6 4531.' 0.1591"


I am guessing a header parameter is wrong but the problem isn't repeatable. Sometimes it works.

I am running scamp v.1.7.0 on a Mac server v.10.5.8, the fits_ldac file is attached. Thanks and cheers, Andy

.fits  lfsr_1178_04_mef.fits (Size: 570.94 KB / Downloads: 10) ]]> <![CDATA[2MASS photometric calibration with scamp and swarp]]> http://www.astromatic.net/forum/showthread.php?tid=747 Fri, 11 Nov 2011 13:14:57 +0000 http://www.astromatic.net/forum/showthread.php?tid=747
I searched hard in the docs and forum for examples of how to setup scamp and swarp to perform the photometric calibration of K-band data. Specifically I am trying to combine VLT-HAWKI mosaics using the 2MASS catalog as reference. I read from the 2007 posts that scamp was not capable of absolute calibration, but surely this must be superseded since scamp accesses the 2MASS database for the astrometric solution.

More precisely, what I need to know is:

1- given a list of input sextractor catalogues, does scamp compute a global photometric solution, or does it solve it catalogue by catalogue? Since I am processing the data OB by OB, I expect the photometric solution to be common to all chips acquired in a single OB.

2- how do I tell swarp to take into account the global phometric solution? I spotted the FSCAL* keywords, but their use is not obvious (i.e. I do not know if to use `FIXED' or `VARIABLE').

Thank you,

Simon Casassus.]]>
I searched hard in the docs and forum for examples of how to setup scamp and swarp to perform the photometric calibration of K-band data. Specifically I am trying to combine VLT-HAWKI mosaics using the 2MASS catalog as reference. I read from the 2007 posts that scamp was not capable of absolute calibration, but surely this must be superseded since scamp accesses the 2MASS database for the astrometric solution.

More precisely, what I need to know is:

1- given a list of input sextractor catalogues, does scamp compute a global photometric solution, or does it solve it catalogue by catalogue? Since I am processing the data OB by OB, I expect the photometric solution to be common to all chips acquired in a single OB.

2- how do I tell swarp to take into account the global phometric solution? I spotted the FSCAL* keywords, but their use is not obvious (i.e. I do not know if to use `FIXED' or `VARIABLE').

Thank you,

Simon Casassus.]]> <![CDATA[Photometry on a list of objects]]> http://www.astromatic.net/forum/showthread.php?tid=742 Fri, 04 Nov 2011 14:10:35 +0000 http://www.astromatic.net/forum/showthread.php?tid=742
Thanks,
Cody]]>
Thanks,
Cody]]> <![CDATA[segfaults when using weight maps]]> http://www.astromatic.net/forum/showthread.php?tid=733 Fri, 21 Oct 2011 19:32:51 +0000 http://www.astromatic.net/forum/showthread.php?tid=733
I'm trying to sextract an image with an associated pixel mask (1s for good pixels, 0s for bad pixels) as a weight map. When I don't use the pixel mask, SExtractor works fine (although it IDs a couple bad pixels as stars):

sex NGC_891_0_277.tr.fc.lc.skysub.flatcorr.msub.geotran.fits -c whirc.sex -WEIGHT_TYPE NONE
----- SExtractor 2.8.6 started on 2011-10-21 at 14:29:35 with 1 thread

Measuring from: "NGC 891 SW BrG45" / 2048 x 2048 / 0 bits FLOATING POINT data
(M+D) Background: 3.53672 RMS: 18.7539 / Threshold: 150.031
Objects: detected 8 / sextracted 6
> All done (in 1 s)

however, when I use the exact same configuration file and image with a weight map, I get this:

sex NGC_891_0_277.tr.fc.lc.skysub.flatcorr.msub.geotran.fits -c whirc.sex -WEIGHT_TYPE MAP_WEIGHT
----- SExtractor 2.8.6 started on 2011-10-21 at 14:30:17 with 1 thread

Measuring from: "NGC 891 SW BrG45" / 2048 x 2048 / 0 bits FLOATING POINT data
Weighting from: "Flat J 32s" / 2048 x 2048 / 0 bits FLOATING POINT data
(M+D) Background: 3.54378 RMS: 18.7265 / Threshold: 149.812
Segmentation fault

I put the fits files for the data image and the pixel mask online, as well as the SExtractor configuration file, online here:

http://www.astro.wisc.edu/~andrew/se_mapweight/

if anyone wants to try to reproduce the problem locally. Any information you could give would be terrific. Thanks!

-Andrew]]>
I'm trying to sextract an image with an associated pixel mask (1s for good pixels, 0s for bad pixels) as a weight map. When I don't use the pixel mask, SExtractor works fine (although it IDs a couple bad pixels as stars):

sex NGC_891_0_277.tr.fc.lc.skysub.flatcorr.msub.geotran.fits -c whirc.sex -WEIGHT_TYPE NONE
----- SExtractor 2.8.6 started on 2011-10-21 at 14:29:35 with 1 thread

Measuring from: "NGC 891 SW BrG45" / 2048 x 2048 / 0 bits FLOATING POINT data
(M+D) Background: 3.53672 RMS: 18.7539 / Threshold: 150.031
Objects: detected 8 / sextracted 6
> All done (in 1 s)

however, when I use the exact same configuration file and image with a weight map, I get this:

sex NGC_891_0_277.tr.fc.lc.skysub.flatcorr.msub.geotran.fits -c whirc.sex -WEIGHT_TYPE MAP_WEIGHT
----- SExtractor 2.8.6 started on 2011-10-21 at 14:30:17 with 1 thread

Measuring from: "NGC 891 SW BrG45" / 2048 x 2048 / 0 bits FLOATING POINT data
Weighting from: "Flat J 32s" / 2048 x 2048 / 0 bits FLOATING POINT data
(M+D) Background: 3.54378 RMS: 18.7265 / Threshold: 149.812
Segmentation fault

I put the fits files for the data image and the pixel mask online, as well as the SExtractor configuration file, online here:

http://www.astro.wisc.edu/~andrew/se_mapweight/

if anyone wants to try to reproduce the problem locally. Any information you could give would be terrific. Thanks!

-Andrew]]> <![CDATA[swarp automatic weighting ]]> http://www.astromatic.net/forum/showthread.php?tid=732 Thu, 20 Oct 2011 19:51:56 +0000 http://www.astromatic.net/forum/showthread.php?tid=732
first of all thank you very much for such fine pieces of software. I am using sextractor, scamp and swarp to combine HAWKI imaging of the Rho Ophiucus cloud into a mosaic. Although I could run the whole sequence to produce a mosaic, I have two serious problems. The first is to do with the scamp solution, which I will post on the scamp threads if I still have not solved it. The second is to do with the way swarp combines the images. Running swarp in its default configuration and with the `MEDIAN' option for the combination produces unsatisfactory results because the gaps in-between detector chips are taken as `zeroes' and included in the median averaging.

From the swarp manual I gathered that in producing the combined mosaic with the `median' alogorithm, the median was taken over all pixels with non-zero weights. It is also said in the swarp manual that swarp has a built-in facillity to do `automatic weighting'. But I could not find the switch to toggle this `automatic weighting'. Your help in finding this `automatic weights' is very much appreciated.

Best regards,

Simon Casassus.]]>
first of all thank you very much for such fine pieces of software. I am using sextractor, scamp and swarp to combine HAWKI imaging of the Rho Ophiucus cloud into a mosaic. Although I could run the whole sequence to produce a mosaic, I have two serious problems. The first is to do with the scamp solution, which I will post on the scamp threads if I still have not solved it. The second is to do with the way swarp combines the images. Running swarp in its default configuration and with the `MEDIAN' option for the combination produces unsatisfactory results because the gaps in-between detector chips are taken as `zeroes' and included in the median averaging.

From the swarp manual I gathered that in producing the combined mosaic with the `median' alogorithm, the median was taken over all pixels with non-zero weights. It is also said in the swarp manual that swarp has a built-in facillity to do `automatic weighting'. But I could not find the switch to toggle this `automatic weighting'. Your help in finding this `automatic weights' is very much appreciated.

Best regards,

Simon Casassus.]]> <![CDATA[Error estimation in v2.8.6]]> http://www.astromatic.net/forum/showthread.php?tid=731 Wed, 19 Oct 2011 16:17:01 +0000 http://www.astromatic.net/forum/showthread.php?tid=731 <![CDATA[scamp 1.7.0 and plplot]]> http://www.astromatic.net/forum/showthread.php?tid=730 Wed, 19 Oct 2011 06:33:22 +0000 http://www.astromatic.net/forum/showthread.php?tid=730
I'm using scamp 1.7.0 installed on a 64 bit linux computer with plplot version 5.9.0, and I'm getting the error message:

scamp: symbol lookup error: scamp: undefined symbol: c_plimage

when trying to make diagnostic plots. Which version of plplot was scamp 1.7.0 tested with? This thread suggests that using plplot version 5.9.4 might work, is this correct?

Thanks for your help!
Neil]]>
I'm using scamp 1.7.0 installed on a 64 bit linux computer with plplot version 5.9.0, and I'm getting the error message:

scamp: symbol lookup error: scamp: undefined symbol: c_plimage

when trying to make diagnostic plots. Which version of plplot was scamp 1.7.0 tested with? This thread suggests that using plplot version 5.9.4 might work, is this correct?

Thanks for your help!
Neil]]> <![CDATA[Stuff documentation]]> http://www.astromatic.net/forum/showthread.php?tid=729 Sun, 16 Oct 2011 15:46:30 +0000 http://www.astromatic.net/forum/showthread.php?tid=729 can someone tell where I can find some documentation for Stuff?I already searched on ADS, but I only found an article on SkyMaker.

Thanks.
Marianna]]> can someone tell where I can find some documentation for Stuff?I already searched on ADS, but I only found an article on SkyMaker.

Thanks.
Marianna]]> <![CDATA[Server down next Tuesday]]> http://www.astromatic.net/forum/showthread.php?tid=727 Sun, 09 Oct 2011 19:07:09 +0000 http://www.astromatic.net/forum/showthread.php?tid=727
because of a scheduled power cut at IAP, the AstrOmatic web site and forum will have to be shutdown on Tuesday Oct 11 (2011) at 8am CET, and will not be available before 6pm CET in the afternoon.
Sorry for this interruption.
- Emmanuel.]]>
because of a scheduled power cut at IAP, the AstrOmatic web site and forum will have to be shutdown on Tuesday Oct 11 (2011) at 8am CET, and will not be available before 6pm CET in the afternoon.
Sorry for this interruption.
- Emmanuel.]]> <![CDATA[Star subtraction with PSF file]]> http://www.astromatic.net/forum/showthread.php?tid=726 Thu, 06 Oct 2011 21:33:42 +0000 http://www.astromatic.net/forum/showthread.php?tid=726 <![CDATA[trouble with rotated images]]> http://www.astromatic.net/forum/showthread.php?tid=725 Wed, 05 Oct 2011 14:47:07 +0000 http://www.astromatic.net/forum/showthread.php?tid=725
I am attempting to use Scamp on some small field-of-view (~3' per side) infrared images. Due to the nature of my observing program the images are all at arbitrary large rotation values, which aren't properly propagated into the image headers. Scamp fails to find the appropriate solution for the images. However, if I edit the CD matrix by hand to have approximately the correct rotation Scamp works fine with the exact same configuration file (and yes, the configuration file has posangle_maxerr set to 180 degrees).

Instead of uploading a bunch of attachments, I've put every relevant file I can think of on this webpage: http://www.astro.wisc.edu/~andrew/scamp. The webpage has two fits images, the original (unrot.fits) and one rotated (rotated.fits). I have also uploaded the configuration files I use for both SExtractor and Scamp. The commands I use on these images to create the other files in that directory are as follows:

sex rotated.fits -c whirc.sex -catalog_name rotated.cat
sex unrot.fits -c whirc.sex -catalog_name unrot.cat
scamp -c scamp.conf rotated.cat >& rotated.log
scamp -c scamp.conf unrot.cat > & unrot.log

Also, I am using Scamp 1.4.0, although from looking at the changelogs I don't see any obvious indication that upgrading to the new version would solve this problem.

If anyone has any ideas or help I would greatly appreciate it. Thanks!

-Andrew]]>
I am attempting to use Scamp on some small field-of-view (~3' per side) infrared images. Due to the nature of my observing program the images are all at arbitrary large rotation values, which aren't properly propagated into the image headers. Scamp fails to find the appropriate solution for the images. However, if I edit the CD matrix by hand to have approximately the correct rotation Scamp works fine with the exact same configuration file (and yes, the configuration file has posangle_maxerr set to 180 degrees).

Instead of uploading a bunch of attachments, I've put every relevant file I can think of on this webpage: http://www.astro.wisc.edu/~andrew/scamp. The webpage has two fits images, the original (unrot.fits) and one rotated (rotated.fits). I have also uploaded the configuration files I use for both SExtractor and Scamp. The commands I use on these images to create the other files in that directory are as follows:

sex rotated.fits -c whirc.sex -catalog_name rotated.cat
sex unrot.fits -c whirc.sex -catalog_name unrot.cat
scamp -c scamp.conf rotated.cat >& rotated.log
scamp -c scamp.conf unrot.cat > & unrot.log

Also, I am using Scamp 1.4.0, although from looking at the changelogs I don't see any obvious indication that upgrading to the new version would solve this problem.

If anyone has any ideas or help I would greatly appreciate it. Thanks!

-Andrew]]>