From gabrielperren at gmail.com  Sun Mar  1 08:42:44 2020
From: gabrielperren at gmail.com (Gabriel Perren)
Date: Sun, 1 Mar 2020 10:42:44 -0300
Subject: [AstroPy] About a few ascii.read() parameters
Message-ID: <CALBDAwAtmt-saW-+cU=UxdbkmCA--H_iQExQsanf1WmxnLo0zw@mail.gmail.com>

Hi all,

I have a quick question: can anyone explain what the do the
*fill_include_names* and *fill_exclude_names* parameters in ascii.read()
<https://docs.astropy.org/en/stable/api/astropy.io.ascii.read.html#astropy.io.ascii.read>
actually do?

I thought they were supposed to include/exclude columns from the
*fill_values* mask, but apparently this is not the case. After playing
around with those parameters for a while I have truly no idea what they are
supposed to do.

Cheers,
Gabriel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20200301/288e7e3f/attachment.html>

From aldcroft at head.cfa.harvard.edu  Sun Mar  1 13:52:29 2020
From: aldcroft at head.cfa.harvard.edu (Aldcroft, Thomas)
Date: Sun, 1 Mar 2020 13:52:29 -0500
Subject: [AstroPy] About a few ascii.read() parameters
In-Reply-To: <CALBDAwAtmt-saW-+cU=UxdbkmCA--H_iQExQsanf1WmxnLo0zw@mail.gmail.com>
References: <CALBDAwAtmt-saW-+cU=UxdbkmCA--H_iQExQsanf1WmxnLo0zw@mail.gmail.com>
Message-ID: <CAMtEP6xEeRwjzJon0PsG+HyzMA72gUFezsZD5CNv9HA6Ud9K6Q@mail.gmail.com>

To close this thread out, it is has moved to
https://github.com/astropy/astropy/issues/10000.

And BTW, congratulations (???) to the astropy project on hitting issue
10000.  Gabriel, you should get some kind of prize!

- Tom

On Sun, Mar 1, 2020 at 8:43 AM Gabriel Perren <gabrielperren at gmail.com>
wrote:

> Hi all,
>
> I have a quick question: can anyone explain what the do the
> *fill_include_names* and *fill_exclude_names* parameters in ascii.read()
> <https://docs.astropy.org/en/stable/api/astropy.io.ascii.read.html#astropy.io.ascii.read>
> actually do?
>
> I thought they were supposed to include/exclude columns from the
> *fill_values* mask, but apparently this is not the case. After playing
> around with those parameters for a while I have truly no idea what they are
> supposed to do.
>
> Cheers,
> Gabriel
> _______________________________________________
> AstroPy mailing list
> AstroPy at python.org
> https://mail.python.org/mailman/listinfo/astropy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20200301/2a011db0/attachment.html>

From gabrielperren at gmail.com  Sun Mar  1 20:01:47 2020
From: gabrielperren at gmail.com (Gabriel Perren)
Date: Sun, 1 Mar 2020 22:01:47 -0300
Subject: [AstroPy] About a few ascii.read() parameters
In-Reply-To: <CAMtEP6xEeRwjzJon0PsG+HyzMA72gUFezsZD5CNv9HA6Ud9K6Q@mail.gmail.com>
References: <CALBDAwAtmt-saW-+cU=UxdbkmCA--H_iQExQsanf1WmxnLo0zw@mail.gmail.com>
 <CAMtEP6xEeRwjzJon0PsG+HyzMA72gUFezsZD5CNv9HA6Ud9K6Q@mail.gmail.com>
Message-ID: <CALBDAwDX47k9-WE4MSUDRKNdLzNqDmhrAJs7xvjpQuKy5m808w@mail.gmail.com>

Thank you Tom!

Also, let's save the prizes for those of you actually closing these issues!

Cheers

El dom., 1 de mar. de 2020 a la(s) 15:52, Aldcroft, Thomas (
aldcroft at head.cfa.harvard.edu) escribi?:

> To close this thread out, it is has moved to
> https://github.com/astropy/astropy/issues/10000.
>
> And BTW, congratulations (???) to the astropy project on hitting issue
> 10000.  Gabriel, you should get some kind of prize!
>
> - Tom
>
> On Sun, Mar 1, 2020 at 8:43 AM Gabriel Perren <gabrielperren at gmail.com>
> wrote:
>
>> Hi all,
>>
>> I have a quick question: can anyone explain what the do the
>> *fill_include_names* and *fill_exclude_names* parameters in ascii.read()
>> <https://docs.astropy.org/en/stable/api/astropy.io.ascii.read.html#astropy.io.ascii.read>
>> actually do?
>>
>> I thought they were supposed to include/exclude columns from the
>> *fill_values* mask, but apparently this is not the case. After playing
>> around with those parameters for a while I have truly no idea what they are
>> supposed to do.
>>
>> Cheers,
>> Gabriel
>> _______________________________________________
>> AstroPy mailing list
>> AstroPy at python.org
>> https://mail.python.org/mailman/listinfo/astropy
>>
> _______________________________________________
> AstroPy mailing list
> AstroPy at python.org
> https://mail.python.org/mailman/listinfo/astropy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20200301/222f287a/attachment.html>

From kellecruz at gmail.com  Mon Mar  2 11:51:30 2020
From: kellecruz at gmail.com (Kelle Cruz)
Date: Mon, 2 Mar 2020 11:51:30 -0500
Subject: [AstroPy] Fwd: [#dotastro] Announcing .Astronomy 12 in Madrid
In-Reply-To: <CAOWaXY9GaQUVXVwa6fuyCdA+Ybb1+_pz+9y=AYYM8boA7VgxWg@mail.gmail.com>
References: <CAOWaXY9GaQUVXVwa6fuyCdA+Ybb1+_pz+9y=AYYM8boA7VgxWg@mail.gmail.com>
Message-ID: <CAApiRV7w8X3G6+hSa+ybhABK-pKvT=zjJduW4j3CefmLpDOb0g@mail.gmail.com>

---------- Forwarded message ---------
From: Robert Simpson <robert.simpson at dotastronomy.com>
Date: Fri, Feb 28, 2020 at 4:01 AM
Subject: [#dotastro] Announcing .Astronomy 12 in Madrid
To: <dotastro at googlegroups.com>


The .Astronomy Foundation is thrilled to announce that *.Astronomy 12 will
be held September 15-17th at ESAC*, near Madrid in Spain. Our hosts are the
ESAC Science Data Centre. ESAC is ESA's science operations centre for all
ESA astronomy, planetary, and heliophysics missions, together with its
scientific archives.

If you?re interested in taking part, use this form to express your interest
in being a part of it
<https://docs.google.com/forms/d/e/1FAIpQLSdmvla8Ma54xNrI5aDnu-WC2Qa9ucbbjiYBEpPghxTylHepKQ/viewform>.
The form closes at the end of March. We will work with ESAC to issue
invites by the end of April 2020.

The conference will include researchers, communicators, educators, data
scientists and those who are all or none of the above. The aim is to be as
inclusive as possible - so if you?d like to spend three days discussing
astronomy and tech, creating and learning new tools, and challenging each
other with new ideas, please apply

We especially encourage you to apply if you?ve never been before. We also
have some funds put aside to support travel and accommodation for a small
number of attendees, (particularly those at an early career stage).

ESAC is an amazing place to host .Astronomy. The archives for the majority
of ESA?s astronomy missions are maintained at ESAC, and the ESDC also
develops ESASky, a science-driven discovery portal. ESAC is home to data
from Gaia as well as XMM-Newton, INTEGRAL, Herschel, Planck, Hubble, and
more.

For this reason, we?re especially interested in participants working in and
around the intersection of data science and archival data exploration. For
example multi-dimensional and multi-messenger data visualization (e.g.
using data cubes from Euclid, JWST, LSST and ALMA); using science
exploitation platforms (e.g. SciServer) in collaborative research; and the
use of machine learning in astronomical data discovery and archival
research.

But those are just guidelines: anyone can apply! We are looking for people
who want to transform the way astronomy is done - especially if their work
is interdisciplinary or unique. So fill out this form
<https://docs.google.com/forms/d/e/1FAIpQLSdmvla8Ma54xNrI5aDnu-WC2Qa9ucbbjiYBEpPghxTylHepKQ/viewform>
(by the end of March) and share it far and wide. We look forward to another
energizing and exciting edition of .Astronomy.

Thanks,

Rob and the .Astronomy Team

-- 
This mailing list (and Google group) is for people who have attended
.Astronomy. Please to keep conversation focussed and be considerate of the
email inboxes of others.
---
You received this message because you are subscribed to the Google Groups
".Astronomy" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to dotastro+unsubscribe at googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/dotastro/CAOWaXY9GaQUVXVwa6fuyCdA%2BYbb1%2B_pz%2B9y%3DAYYM8boA7VgxWg%40mail.gmail.com
<https://groups.google.com/d/msgid/dotastro/CAOWaXY9GaQUVXVwa6fuyCdA%2BYbb1%2B_pz%2B9y%3DAYYM8boA7VgxWg%40mail.gmail.com?utm_medium=email&utm_source=footer>
.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20200302/518ebf35/attachment-0001.html>

From kellecruz at gmail.com  Mon Mar  9 13:26:13 2020
From: kellecruz at gmail.com (Kelle Cruz)
Date: Mon, 9 Mar 2020 13:26:13 -0400
Subject: [AstroPy] Interest in work on Kepler/K2 data, lightkurve,
 and astropy timeseries?
In-Reply-To: <CAApiRV7hYeoWya3o5rr2QxM_KsXWg+4t0hZfz3fDDdcsn+a_2A@mail.gmail.com>
References: <CAApiRV7hYeoWya3o5rr2QxM_KsXWg+4t0hZfz3fDDdcsn+a_2A@mail.gmail.com>
Message-ID: <CAApiRV4ja8H8F-5+A6AeM=FKe3TYv4sOKfPYuOQBnOFoce4NpA@mail.gmail.com>

NumFocus, via a contract with STScI and in collaboration with the Astropy
Project, is seeking multiple full and part-time contractors.

================

Kepler and K2 Training Materials Developer

We are seeking a contractor or contractors to develop training materials
for the resources available in the Python programming language for the
analysis of Kepler and K2 data. These training materials should include
introductory material, noise removal, and applying machine learning and
cloud computing to the Kepler and K2 data (
https://registry.opendata.aws/kepler/).

Ideal candidates would have experience with Kepler and K2 data and the
Lightkurve package. Experience with machine learning cloud computing is
also a plus. Past experience with developing training materials is not
required but an ideal candidate would have a demonstrated interest in
computational training.

================

Lightkurve and Astropy Timeseries Software Developer

We are seeking a contractor or contractors to improve the compatibility
between the Lightkurve package and the astropy timeseries subpackage.
Specifically, remove duplicate/deprecated code from LightKurve as a result
of leveraging the TimeSeries object, and to extend/enhance timeseries to
better support Kepler data.

Ideal candidates would have experience with Kepler and K2 data, the
Lightkurve package, the astropy timeseries subpackage, and software
development via GitHub.

===================

These services are expected to be completed remotely and contractors will
be expected to participate in regular telecons. Contractors will be
expected to abide by the NumFocus and Astropy Codes of Conduct.

Compensation will be hourly at a rate of $75?130/hour, depending on
experience. The work needs to be completed by Sept 30, 2020 so we are
particularly interested in candidates who are available to start work
immediately. All applications received by April 7 will receive full
consideration.

To apply, please send an email to kellecruz at gmail.com with a resume
attached and a description of your interest in the role in the body of the
email. Also include specific examples of relevant experience and its
outcomes (e.g. include screenshots, links to pull requests). Please also
describe your availability between now and Sept 30, 2020.


Kelle

--
Kelle Cruz, PhD
917.837.9748 ? Hunter: x16486 ? AMNH: x7930
Pronouns: she/her and they/them



On Thu, Oct 24, 2019 at 3:31 PM Kelle Cruz <kellecruz at gmail.com> wrote:

> Hi Astro Data/Stats folks,
>
> I am helping out some folks who have a pot of money available for work on
> developing software and/or tutorials related to Kepler, lightKurve, and
> potentially the new astropy time series module.
>
> We're looking  for folks
> - interested in working on making Kepler data more accessible to machine
> learning techniques via writing new software and/or tutorials.
> - who could potentially take the lead on a Kaggle challenge related to ML
> and Kepler.
>
> Please let me know if you're interested in this or have any nominations.
>
> Thanks,
> Kelle
>
> --
> Kelle Cruz, PhD
> 917.725.1334 ? Hunter: x16486 ? AMNH: x7930
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20200309/659f283c/attachment.html>

From pslowater at gmail.com  Tue Mar 24 06:14:13 2020
From: pslowater at gmail.com (Peter)
Date: Tue, 24 Mar 2020 21:14:13 +1100
Subject: [AstroPy] RA/Dec to Alt/Az
Message-ID: <CAEratZFyCvihyKtnGY2idL4tbh7fJgEsdcKw2WLPGAkg1B1RRQ@mail.gmail.com>

I am using Stellarium to point a custom mount at the selected object which
at this time I am just testing rotation and using the sun & shadow.
Using the code below from samples it receives the dec/asc and calculates
the alt/az.
The problem I have is that when the sun is northish the az is close to what
Stellarium shows but when east or west then the az is about 8 Deg or more
off in the calculation compared to Stellarium and the Shadow also is not
correct.
I assume it's the way I am doing the calc, does what I have look correct?
The RA/DEC from Stellarium is J2000 from what I can work out.

Peter..

           dec_in = float(vals[2])
           asc_in= float(vals[1])
           M42 = SkyCoord(ra=float(vals[1])*u.degree,
dec=float(vals[2])*u.degree, frame='icrs')
           home = EarthLocation(lat=-38.06395*u.deg, lon=145.28455*u.deg,
height=40*u.m)
           utcoffset = +11*u.hour  # Eastern Daylight Time
           time = Time(datetime.datetime.now())
           print("Time           :",time)
           time = Time(datetime.datetime.now())- utcoffset
           print("Time UTC       :",time)
           m33altaz = M42.transform_to(AltAz(obstime=time,location=home))
           print(dec_in," : ",asc_in)
           print("Postion to
move:",numpy.around((m33altaz.alt*u.deg).value,3),"  : ",numpy.around((
m33altaz.az*u.deg).value,3))
           print("====")
           rotation = numpy.around((m33altaz.az*u.deg).value,3)
           angle = numpy.around((m33altaz.alt*u.deg).value,3)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20200324/03845c0b/attachment.html>

From ejensen1 at swarthmore.edu  Tue Mar 24 08:37:42 2020
From: ejensen1 at swarthmore.edu (Eric Jensen)
Date: Tue, 24 Mar 2020 08:37:42 -0400
Subject: [AstroPy] RA/Dec to Alt/Az
In-Reply-To: <CAEratZFyCvihyKtnGY2idL4tbh7fJgEsdcKw2WLPGAkg1B1RRQ@mail.gmail.com>
References: <CAEratZFyCvihyKtnGY2idL4tbh7fJgEsdcKw2WLPGAkg1B1RRQ@mail.gmail.com>
Message-ID: <841146E7-4D96-4570-BCAE-F3FB009AD0C2@swarthmore.edu>

Hi Peter,

You could try the get_sun function in astropy to be sure you?ve got accurate coordinates for the Sun, and go from there. 

How are you judging true north / south?  If using a compass, be sure to correct for magnetic vs. true north. 

Note that the apparent position of the Sun in the sky gets shifted by atmospheric refraction when it is low in the sky, but I think that effect is too small to explain what you?re seeing (and would be mostly in altitude). 

Good luck,

Eric

P.S. The ?Eastern Daylight Time? comment in your code confused me for a bit - might want to change that, as it looks like you?re in Melbourne...

>> On Mar 24, 2020, at 6:14 AM, Peter <pslowater at gmail.com> wrote:
> ?
> I am using Stellarium to point a custom mount at the selected object which at this time I am just testing rotation and using the sun & shadow.
> Using the code below from samples it receives the dec/asc and calculates the alt/az.
> The problem I have is that when the sun is northish the az is close to what Stellarium shows but when east or west then the az is about 8 Deg or more off in the calculation compared to Stellarium and the Shadow also is not correct.
> I assume it's the way I am doing the calc, does what I have look correct?
> The RA/DEC from Stellarium is J2000 from what I can work out.
> 
> Peter..
> 
>            dec_in = float(vals[2])
>            asc_in= float(vals[1])
>            M42 = SkyCoord(ra=float(vals[1])*u.degree, dec=float(vals[2])*u.degree, frame='icrs') 
>            home = EarthLocation(lat=-38.06395*u.deg, lon=145.28455*u.deg, height=40*u.m)
>            utcoffset = +11*u.hour  # Eastern Daylight Time
>            time = Time(datetime.datetime.now())
>            print("Time           :",time)
>            time = Time(datetime.datetime.now())- utcoffset
>            print("Time UTC       :",time)
>            m33altaz = M42.transform_to(AltAz(obstime=time,location=home))
>            print(dec_in," : ",asc_in)
>            print("Postion to move:",numpy.around((m33altaz.alt*u.deg).value,3),"  : ",numpy.around((m33altaz.az*u.deg).value,3))
>            print("====")
>            rotation = numpy.around((m33altaz.az*u.deg).value,3)
>            angle = numpy.around((m33altaz.alt*u.deg).value,3)
> _______________________________________________
> AstroPy mailing list
> AstroPy at python.org
> https://mail.python.org/mailman/listinfo/astropy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20200324/f14d7b25/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2275 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/astropy/attachments/20200324/f14d7b25/attachment.bin>

From pslowater at gmail.com  Tue Mar 24 16:17:49 2020
From: pslowater at gmail.com (Peter)
Date: Wed, 25 Mar 2020 07:17:49 +1100
Subject: [AstroPy] RA/Dec to Alt/Az
Message-ID: <CAEratZG5BaO7J02nqgpwm+0_1oD-LBOZoS7me1iJvUrGXMxn-A@mail.gmail.com>

Hi Eric,

I am telling the mount to point to the sun then align the shadow with
that, I am not using a  compass as I expect if all calcs are correct
that would work as well.

I will try the get_sun today.

Sorry about the utcoffset I had missed that tidy up but yes in Melbourne.

So from what you see approach for the calculation looks correct?

Peter..

From pslowater at gmail.com  Wed Mar 25 04:48:31 2020
From: pslowater at gmail.com (Peter)
Date: Wed, 25 Mar 2020 19:48:31 +1100
Subject: [AstroPy] RA/Dec to Alt/Az
In-Reply-To: <CAEratZG5BaO7J02nqgpwm+0_1oD-LBOZoS7me1iJvUrGXMxn-A@mail.gmail.com>
References: <CAEratZG5BaO7J02nqgpwm+0_1oD-LBOZoS7me1iJvUrGXMxn-A@mail.gmail.com>
Message-ID: <CAEratZEEOTjovBWfivV4WMiQtP1_V9ZYBT=7=9rna-VyipSCeg@mail.gmail.com>

Hi Eric,

I tried with the get_sun and I see a different of about .009 degrees
so it's close.
I did just notice a large time drift on Stellarium and I need to test
again ensure the time is correct.

Peter..

On Wed, Mar 25, 2020 at 7:17 AM Peter <pslowater at gmail.com> wrote:
>
> Hi Eric,
>
> I am telling the mount to point to the sun then align the shadow with
> that, I am not using a  compass as I expect if all calcs are correct
> that would work as well.
>
> I will try the get_sun today.
>
> Sorry about the utcoffset I had missed that tidy up but yes in Melbourne.
>
> So from what you see approach for the calculation looks correct?
>
> Peter..

From laurent.michel at astro.unistra.fr  Wed Mar 25 05:56:10 2020
From: laurent.michel at astro.unistra.fr (Laurent MICHEL)
Date: Wed, 25 Mar 2020 10:56:10 +0100
Subject: [AstroPy] Handling IRAF@ccmap astrometry solution with Astropy
Message-ID: <353f1dda-d859-5c87-1124-6f3f2c93677d@astro.unistra.fr>

Dear Astropy,

In the project I'm working on (SVOM), I have to resolve image astrometry 
with parameters given as IRAF at ccmap input files (*.db).
I've pasted a sample below.
As I'm not an IRAF user and my application is Python based, I would like 
to know whether someone in the community would have some experience with 
handling such coordinate transformations with AstroPy or some associate 
package.

Regards
LM

> begin	first
> 	xrefmean	1006.983846153846
> 	yrefmean	1295.986153846154
> 	lngmean		51.92749369230773
> 	latmean		46.71962446153846
> 	pixsystem	logical
> 	coosystem	j2000
> 	projection	tan
> 	lngref		51.92764538984333
> 	latref		46.71980701217847
> 	lngunits	degrees
> 	latunits	degrees
> 	xpixref		1006.538812424377
> 	ypixref		1296.240113815674
> 	geometry	general
> 	function	legendre
> 	xishift		785.057480503327
> 	etashift	-1011.192209060798
> 	xmag		0.780016468878781
> 	ymag		0.7800388866873553
> 	xrotation	180.0054358489221
> 	yrotation	0.003364033436420988
> 	wcsxirms	0.03777045679395438
> 	wcsetarms	0.04621390005594472
> 	xirms		0.02446609811977102
> 	etarms		0.03292506146030702
> 	surface1	11
> 			2.	2.
> 			2.	2.
> 			2.	2.
> 			0.	0.
> 			1.	1.
> 			2048.	2048.
> 			1.	1.
> 			2048.	2048.
> 			-14.02246741249724	-211.9665257906808
> 			-798.346852301705	0.07577120489887789
> 			0.04687505246502031	798.3697991484097
> 	surface2	14
> 			2.	2.
> 			3.	3.
> 			3.	3.
> 			2.	2.
> 			1.	1.
> 			2048.	2048.
> 			1.	1.
> 			2048.	2048.
> 			0.01209115687180025	-0.01371667420039151
> 			-0.001595934377758362	0.01973382792045219
> 			0.01870940742458613	-0.03495580079513902
> 			-0.04682685192837127	0.05029843125259523
> 			0.02206659476379174	-0.06407294737100595
> 			0.09651497861498953	-0.103465418301487
> # Fri 10:57:09 13-Mar-2020



-- 
---- Laurent MICHEL              Tel  (33 0) 3 68 85 24 37
      Observatoire de Strasbourg  Fax  (33 0) 3 68 85 24 32
      11 Rue de l'Universite      Mail laurent.michel at astro.unistra.fr
      67000 Strasbourg (France)   Web  http://astro.u-strasbg.fr/~michel
---

From j.armstrong.2 at research.gla.ac.uk  Wed Mar 25 10:07:23 2020
From: j.armstrong.2 at research.gla.ac.uk (John Armstrong (PGR))
Date: Wed, 25 Mar 2020 14:07:23 +0000
Subject: [AstroPy] WCS with non-uniform axis
Message-ID: <0D2A61ED-18D5-448B-88E4-9CE8B7BC79D0@research.gla.ac.uk>

Hi all,

I am currently trying to construct a custom WCS for imaging spectropolarimetric observations I have. The wavelengths sampled are not uniform across the spectral line (the wings are sampled more coarsely than the core) and therefore, there is no cdelt for the wavelength axis. Is there a way for me to tell the WCS object what the wavelength values are at each point? As I understand the WCS construction, you give the constructor a central wavelength, the length of the axis and the cdelt for that axis, is there a way to still construct the wavelength axis by giving it an array of wavelengths rather than cdelt?

Thanks for any help/insights you may be able to offer. Hope everyone is staying safe and healthy.

Kind regards,
John
--------------------------------------------
Mr. John Armstrong (he/him), FRAS MSci
PhD Student, Astronomy & Astrophysics Group,
Schools of Physics & Astronomy,
Kelvin Building (room 604),

University of Glasgow, Glasgow G12 8QQ, UK
E: j.armstrong.2 at research.gla.ac.uk<mailto:j.armstrong.2 at research.gla.ac.uk>




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20200325/d8de602a/attachment.html>

From jjk at uvic.ca  Wed Mar 25 11:15:59 2020
From: jjk at uvic.ca (JJ Kavelaars)
Date: Wed, 25 Mar 2020 08:15:59 -0700
Subject: [AstroPy] Handling IRAF@ccmap astrometry solution with Astropy
In-Reply-To: <353f1dda-d859-5c87-1124-6f3f2c93677d@astro.unistra.fr>
References: <353f1dda-d859-5c87-1124-6f3f2c93677d@astro.unistra.fr>
Message-ID: <1293F4CA-1BD0-4395-BA2E-3D277FE04A5C@uvic.ca>

Hi,

If you have access to IRAF you can use the ccsetwcs to put the ccmap database version of the WCS into the FITS header:

http://iraf.noao.edu/scripts/irafhelp?ccsetwcs <http://iraf.noao.edu/scripts/irafhelp?ccsetwcs>

Then astropy will understand the WCS.  But that will only provide the linear components. 

JJ


> On Mar 25, 2020, at 2:56 AM, Laurent MICHEL <laurent.michel at astro.unistra.fr> wrote:
> 
> Dear Astropy,
> 
> In the project I'm working on (SVOM), I have to resolve image astrometry with parameters given as IRAF at ccmap input files (*.db).
> I've pasted a sample below.
> As I'm not an IRAF user and my application is Python based, I would like to know whether someone in the community would have some experience with handling such coordinate transformations with AstroPy or some associate package.
> 
> Regards
> LM
> 
>> begin	first
>> 	xrefmean	1006.983846153846
>> 	yrefmean	1295.986153846154
>> 	lngmean		51.92749369230773
>> 	latmean		46.71962446153846
>> 	pixsystem	logical
>> 	coosystem	j2000
>> 	projection	tan
>> 	lngref		51.92764538984333
>> 	latref		46.71980701217847
>> 	lngunits	degrees
>> 	latunits	degrees
>> 	xpixref		1006.538812424377
>> 	ypixref		1296.240113815674
>> 	geometry	general
>> 	function	legendre
>> 	xishift		785.057480503327
>> 	etashift	-1011.192209060798
>> 	xmag		0.780016468878781
>> 	ymag		0.7800388866873553
>> 	xrotation	180.0054358489221
>> 	yrotation	0.003364033436420988
>> 	wcsxirms	0.03777045679395438
>> 	wcsetarms	0.04621390005594472
>> 	xirms		0.02446609811977102
>> 	etarms		0.03292506146030702
>> 	surface1	11
>> 			2.	2.
>> 			2.	2.
>> 			2.	2.
>> 			0.	0.
>> 			1.	1.
>> 			2048.	2048.
>> 			1.	1.
>> 			2048.	2048.
>> 			-14.02246741249724	-211.9665257906808
>> 			-798.346852301705	0.07577120489887789
>> 			0.04687505246502031	798.3697991484097
>> 	surface2	14
>> 			2.	2.
>> 			3.	3.
>> 			3.	3.
>> 			2.	2.
>> 			1.	1.
>> 			2048.	2048.
>> 			1.	1.
>> 			2048.	2048.
>> 			0.01209115687180025	-0.01371667420039151
>> 			-0.001595934377758362	0.01973382792045219
>> 			0.01870940742458613	-0.03495580079513902
>> 			-0.04682685192837127	0.05029843125259523
>> 			0.02206659476379174	-0.06407294737100595
>> 			0.09651497861498953	-0.103465418301487
>> # Fri 10:57:09 13-Mar-2020
> 
> 
> 
> -- 
> ---- Laurent MICHEL              Tel  (33 0) 3 68 85 24 37
>     Observatoire de Strasbourg  Fax  (33 0) 3 68 85 24 32
>     11 Rue de l'Universite      Mail laurent.michel at astro.unistra.fr
>     67000 Strasbourg (France)   Web  http://astro.u-strasbg.fr/~michel
> ---
> _______________________________________________
> AstroPy mailing list
> AstroPy at python.org
> https://mail.python.org/mailman/listinfo/astropy

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20200325/cd43fdb9/attachment-0001.html>

From laurent.michel at astro.unistra.fr  Fri Mar 27 05:49:42 2020
From: laurent.michel at astro.unistra.fr (Laurent MICHEL)
Date: Fri, 27 Mar 2020 10:49:42 +0100
Subject: [AstroPy] Handling IRAF@ccmap astrometry solution with Astropy
In-Reply-To: <1293F4CA-1BD0-4395-BA2E-3D277FE04A5C@uvic.ca>
References: <353f1dda-d859-5c87-1124-6f3f2c93677d@astro.unistra.fr>
 <1293F4CA-1BD0-4395-BA2E-3D277FE04A5C@uvic.ca>
Message-ID: <cf50b4d2-163c-8c47-8395-1d762f750943@astro.unistra.fr>

Hi,

Thank you for your reply.
Unfortunately, my projection contains a non linear component (legendre 
polynoms).
I'll try anyway.

LM

Le 25/03/2020 ? 16:15, JJ Kavelaars a ?crit?:
> Hi,
> 
> If you have access to IRAF you can use the ccsetwcs to put the ccmap 
> database version of the WCS into the FITS header:
> 
> http://iraf.noao.edu/scripts/irafhelp?ccsetwcs
> 
> Then astropy will understand the WCS. ?But that will only provide the 
> linear components.
> 
> JJ
> 
> 
>> On Mar 25, 2020, at 2:56 AM, Laurent MICHEL 
>> <laurent.michel at astro.unistra.fr 
>> <mailto:laurent.michel at astro.unistra.fr>> wrote:
>>
>> Dear Astropy,
>>
>> In the project I'm working on (SVOM), I have to resolve image 
>> astrometry with parameters given as IRAF at ccmap input files (*.db).
>> I've pasted a sample below.
>> As I'm not an IRAF user and my application is Python based, I would 
>> like to know whether someone in the community would have some 
>> experience with handling such coordinate transformations with AstroPy 
>> or some associate package.
>>
>> Regards
>> LM
>>
>>> beginfirst
>>> xrefmean1006.983846153846
>>> yrefmean1295.986153846154
>>> lngmean51.92749369230773
>>> latmean46.71962446153846
>>> pixsystemlogical
>>> coosystemj2000
>>> projectiontan
>>> lngref51.92764538984333
>>> latref46.71980701217847
>>> lngunitsdegrees
>>> latunitsdegrees
>>> xpixref1006.538812424377
>>> ypixref1296.240113815674
>>> geometrygeneral
>>> functionlegendre
>>> xishift785.057480503327
>>> etashift-1011.192209060798
>>> xmag0.780016468878781
>>> ymag0.7800388866873553
>>> xrotation180.0054358489221
>>> yrotation0.003364033436420988
>>> wcsxirms0.03777045679395438
>>> wcsetarms0.04621390005594472
>>> xirms0.02446609811977102
>>> etarms0.03292506146030702
>>> surface111
>>> 2.2.
>>> 2.2.
>>> 2.2.
>>> 0.0.
>>> 1.1.
>>> 2048.2048.
>>> 1.1.
>>> 2048.2048.
>>> -14.02246741249724-211.9665257906808
>>> -798.3468523017050.07577120489887789
>>> 0.04687505246502031798.3697991484097
>>> surface214
>>> 2.2.
>>> 3.3.
>>> 3.3.
>>> 2.2.
>>> 1.1.
>>> 2048.2048.
>>> 1.1.
>>> 2048.2048.
>>> 0.01209115687180025-0.01371667420039151
>>> -0.0015959343777583620.01973382792045219
>>> 0.01870940742458613-0.03495580079513902
>>> -0.046826851928371270.05029843125259523
>>> 0.02206659476379174-0.06407294737100595
>>> 0.09651497861498953-0.103465418301487
>>> # Fri 10:57:09 13-Mar-2020
>>
>>
>>
>> -- 
>> ---- Laurent MICHEL ?????????????Tel ?(33 0) 3 68 85 24 37
>> ????Observatoire de Strasbourg ?Fax ?(33 0) 3 68 85 24 32
>> ????11 Rue de l'Universite ?????Mail laurent.michel at astro.unistra.fr 
>> <mailto:laurent.michel at astro.unistra.fr>
>> ????67000 Strasbourg (France) ??Web http://astro.u-strasbg.fr/~michel
>> ---
>> _______________________________________________
>> AstroPy mailing list
>> AstroPy at python.org <mailto:AstroPy at python.org>
>> https://mail.python.org/mailman/listinfo/astropy
> 
> 
> _______________________________________________
> AstroPy mailing list
> AstroPy at python.org
> https://mail.python.org/mailman/listinfo/astropy
> 

-- 
---- Laurent MICHEL              Tel  (33 0) 3 68 85 24 37
      Observatoire de Strasbourg  Fax  (33 0) 3 68 85 24 32
      11 Rue de l'Universite      Mail laurent.michel at astro.unistra.fr
      67000 Strasbourg (France)   Web  http://astro.u-strasbg.fr/~michel
---