From jimmyboysingh at gmail.com Fri Oct 1 06:41:51 2021 From: jimmyboysingh at gmail.com (Jim Singh) Date: Fri, 1 Oct 2021 20:41:51 +1000 Subject: [AstroPy] Question re tilt of Saturn's rings Message-ID: Hi, I've been using astropy with JPL Horizons ephemeris system to plot the positions of planets and their moons. For Saturn, would also like to plot the angle of the rings as seen from Earth, but do not know which field(s) to query (if indeed this can be determined from said system). So seeking your kind advice. Regards, Jim -------------- next part -------------- An HTML attachment was scrubbed... URL: From productnews at hvf.ch Mon Oct 4 13:13:37 2021 From: productnews at hvf.ch (Productnews) Date: Mon, 4 Oct 2021 19:13:37 +0200 Subject: [AstroPy] astropy.time.Time fails for lapse days in year -100 and earlier Message-ID: <5a7f5ab8-447b-29c2-bced-53d03678427a@hvf.ch> I am using astropy.time.Time() to extend the standard datetime.datetime() functionality into the B.C. range of years. I realize that lapse days (February 29) are only supported from now to the year -96, but not for the year -100 and earlier. Examples: Date in fits format??? ??? ??? Julian Day -00096-02-28T00:00:00? =? 1686051.5??? year -96 -00096-02-29T00:00:00? =? 1686052.5 -00096-03-01T00:00:00? =? 1686053.5 -00100-02-28T12:00:00? =? 1684591.0??? year -100 -00100-03-01T12:00:00? =? 1684593.0 We see that 2 Julian Days are between -100-02-28 and -100-03-01 Now we convert from Julian Day to fits format date: Julian Day??? Date in fits format 1686051.5? =? -00096-02-28T00:00:00.000??????? correct inverses to above 1686052.5? =? -00096-02-29T00:00:00.000 1686053.5? =? -00096-03-01T00:00:00.000 1684591.0? =? -00100-02-28T12:00:00.000 1684592.0? =? -00100-03-01T12:00:00.000?????? two different Julian Days map to the same calendar day 1684593.0? =? -00100-03-01T12:00:00.000 I find nowhere a description of this apparent inconsistency. Could someone explain or provide a patch? Thanks, Harald From abostroem at gmail.com Mon Oct 4 15:14:12 2021 From: abostroem at gmail.com (Azalee Bostroem) Date: Mon, 4 Oct 2021 12:14:12 -0700 Subject: [AstroPy] Tying model bounds to other parameters in compound models Message-ID: Hi, I am trying to fit the [OI] doublet at 6300, 6364 A as a compound model (Const1D+Gaussian1D+Gaussian1D). This doublet has a known ratio range of 1:1 to 1:3 and I would like fix the bounds of the amplitude of the second gaussian to be between 1/3 and 1 times the amplitude of the first gaussian. I know its possible to tie model parameters to each other (e.g. def fix_offset(oi_emission): mean_2 = oi_emission.mean_1 + 64 return mean_2 emission_model.mean_2.tied = fix_offset ) and to set bounds on parameters (e.g. emission_model.amplitude_1.min = 0 ). Is it possible to tie bounds to other parameters? My naive approach of def fixed_amp_ratio(oi_emission): amplitude_2.min = 0.3*oi_emission.amplitude_1 return amplitude2.min emission_model.amplitude_2.min.tied = fixed_amp_ratio Didn?t work because min has no attribute tied. Please let me know if I?ve missed anything, Thanks, Azalee -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmoustakas at siena.edu Tue Oct 5 15:02:07 2021 From: jmoustakas at siena.edu (Moustakas, John) Date: Tue, 5 Oct 2021 15:02:07 -0400 Subject: [AstroPy] Tying model bounds to other parameters in compound models In-Reply-To: References: Message-ID: Hi Azalee-- Perhaps other power users can give you a solution, but my take of the code base is that what you're trying to do is not possible. I believe you're going to have to add a new Parameter which is the amplitude ratio of the two lines, and put bounds on that parameter. The amplitude of the weaker component of the doublet will then be the ratio times the amplitude of the stronger component (effectively leaving you with the same number of free parameters). In case it's helpful you're welcome to use some or all of the line-fitting code I put together as part of this ticket (see the zip file in the body of the issue)-- https://github.com/astropy/astropy/issues/12089#issue-974636724 Good luck! Cheers, -John -- John Moustakas, PhD Associate Professor & Department Chair Department of Physics & Astronomy Siena College 515 Loudon Road Loudonville, NY 12211 518-783-4274 jmoustakas at siena.edu Pronouns: he|him|his On Mon, Oct 4, 2021 at 3:14 PM Azalee Bostroem wrote: > > Hi, > > I am trying to fit the [OI] doublet at 6300, 6364 A as a compound model (Const1D+Gaussian1D+Gaussian1D). This doublet has a known ratio range of 1:1 to 1:3 and I would like fix the bounds of the amplitude of the second gaussian to be between 1/3 and 1 times the amplitude of the first gaussian. I know its possible to tie model parameters to each other (e.g. > > def fix_offset(oi_emission): > mean_2 = oi_emission.mean_1 + 64 > return mean_2 > > emission_model.mean_2.tied = fix_offset > > ) and to set bounds on parameters (e.g. > > emission_model.amplitude_1.min = 0 > > ). Is it possible to tie bounds to other parameters? My naive approach of > > def fixed_amp_ratio(oi_emission): > amplitude_2.min = 0.3*oi_emission.amplitude_1 > return amplitude2.min > > emission_model.amplitude_2.min.tied = fixed_amp_ratio > > Didn?t work because min has no attribute tied. > > Please let me know if I?ve missed anything, > > Thanks, > Azalee > _______________________________________________ > AstroPy mailing list > AstroPy at python.org > https://mail.python.org/mailman/listinfo/astropy From erik.m.bray at gmail.com Fri Oct 8 11:39:05 2021 From: erik.m.bray at gmail.com (E. Madison Bray) Date: Fri, 8 Oct 2021 17:39:05 +0200 Subject: [AstroPy] Tying model bounds to other parameters in compound models In-Reply-To: References: Message-ID: Hi Azalee, I'm not sure if this would actually work, but instead of using a "min" bound you could effectively use tied to implement a (dynamic) bound, something like: ``` def fixed_amp_ratio(oi_emission): return min(oi_emission.amplitude_2, 0.3 * oe_emission.amplitude_1) emission_model.amplitude_2.tied = fixed_amp_ratio ``` Or, as you wrote: > I would like fix the bounds of the amplitude of the second gaussian to be between 1/3 and 1 times the amplitude of the first gaussian You could do something like: ``` def fixed_amp_ratio(oi_emission): return max(min(oi_emission.amplitude_2, 0.3 * oi_emission.amplitude_1), oi_emssion.amplitude_1) ``` That should keep 0.3*A_1 < A_2, < A_1. John's answer might make more sense, but I thought this seemed like a simple possibility, since in some ways the way upper/lower bounds are evaluated are just a special case of "tied". On Mon, Oct 4, 2021 at 9:14 PM Azalee Bostroem wrote: > > Hi, > > I am trying to fit the [OI] doublet at 6300, 6364 A as a compound model (Const1D+Gaussian1D+Gaussian1D). This doublet has a known ratio range of 1:1 to 1:3 and I would like fix the bounds of the amplitude of the second gaussian to be between 1/3 and 1 times the amplitude of the first gaussian. I know its possible to tie model parameters to each other (e.g. > > def fix_offset(oi_emission): > mean_2 = oi_emission.mean_1 + 64 > return mean_2 > > emission_model.mean_2.tied = fix_offset > > ) and to set bounds on parameters (e.g. > > emission_model.amplitude_1.min = 0 > > ). Is it possible to tie bounds to other parameters? My naive approach of > > def fixed_amp_ratio(oi_emission): > amplitude_2.min = 0.3*oi_emission.amplitude_1 > return amplitude2.min > > emission_model.amplitude_2.min.tied = fixed_amp_ratio > > Didn?t work because min has no attribute tied. > > Please let me know if I?ve missed anything, > > Thanks, > Azalee > _______________________________________________ > AstroPy mailing list > AstroPy at python.org > https://mail.python.org/mailman/listinfo/astropy From erik.m.bray at gmail.com Fri Oct 8 11:40:11 2021 From: erik.m.bray at gmail.com (E. Madison Bray) Date: Fri, 8 Oct 2021 17:40:11 +0200 Subject: [AstroPy] Tying model bounds to other parameters in compound models In-Reply-To: References: Message-ID: Of course just as soon as I hit send I realized I had the min() and max() calls backwards, but you get the idea :-) On Fri, Oct 8, 2021 at 5:39 PM E. Madison Bray wrote: > > Hi Azalee, > > I'm not sure if this would actually work, but instead of using a "min" > bound you could effectively use tied to implement a (dynamic) bound, > something like: > > ``` > def fixed_amp_ratio(oi_emission): > return min(oi_emission.amplitude_2, 0.3 * oe_emission.amplitude_1) > > emission_model.amplitude_2.tied = fixed_amp_ratio > ``` > > Or, as you wrote: > > > I would like fix the bounds of the amplitude of the second gaussian to be between 1/3 and 1 times the amplitude of the first gaussian > > You could do something like: > > ``` > def fixed_amp_ratio(oi_emission): > return max(min(oi_emission.amplitude_2, 0.3 * > oi_emission.amplitude_1), oi_emssion.amplitude_1) > ``` > > That should keep 0.3*A_1 < A_2, < A_1. > > John's answer might make more sense, but I thought this seemed like a > simple possibility, since in some ways the way upper/lower bounds are > evaluated are just a special case of "tied". > > On Mon, Oct 4, 2021 at 9:14 PM Azalee Bostroem wrote: > > > > Hi, > > > > I am trying to fit the [OI] doublet at 6300, 6364 A as a compound model (Const1D+Gaussian1D+Gaussian1D). This doublet has a known ratio range of 1:1 to 1:3 and I would like fix the bounds of the amplitude of the second gaussian to be between 1/3 and 1 times the amplitude of the first gaussian. I know its possible to tie model parameters to each other (e.g. > > > > def fix_offset(oi_emission): > > mean_2 = oi_emission.mean_1 + 64 > > return mean_2 > > > > emission_model.mean_2.tied = fix_offset > > > > ) and to set bounds on parameters (e.g. > > > > emission_model.amplitude_1.min = 0 > > > > ). Is it possible to tie bounds to other parameters? My naive approach of > > > > def fixed_amp_ratio(oi_emission): > > amplitude_2.min = 0.3*oi_emission.amplitude_1 > > return amplitude2.min > > > > emission_model.amplitude_2.min.tied = fixed_amp_ratio > > > > Didn?t work because min has no attribute tied. > > > > Please let me know if I?ve missed anything, > > > > Thanks, > > Azalee > > _______________________________________________ > > AstroPy mailing list > > AstroPy at python.org > > https://mail.python.org/mailman/listinfo/astropy From nadvornik.ji at gmail.com Thu Oct 14 04:44:14 2021 From: nadvornik.ji at gmail.com (=?UTF-8?B?SmnFmcOtIE7DoWR2b3Juw61r?=) Date: Thu, 14 Oct 2021 10:44:14 +0200 Subject: [AstroPy] Reading FITS uncompressed headers performance Message-ID: Hi all, I am a little confused about the performance of astropy.io.fits when trying to open just the primary header of a compressed (.bz2) FITS file. The header is uncompressed plain text, correctly ended by the END tag. Is there some setting that I need to use to parse the header without needing to decompress the whole file? Thank you, Jiri N. -------------- next part -------------- An HTML attachment was scrubbed... URL: From eperez at iaa.es Thu Oct 14 05:17:42 2021 From: eperez at iaa.es (eperez) Date: Thu, 14 Oct 2021 11:17:42 +0200 Subject: [AstroPy] datetime and timestamp Message-ID: <08AD8EEC-77D5-424C-9F8B-BAE87C131E0E@iaa.es> I get an inconsistent result when translating datetime to timestamp: A later date gives a lower timestamp: tehere is a jump backwards: In : time.mktime(datetime(2021, 3, 28, 2, 40).timetuple()) Out: 1616895600.0 In : time.mktime(datetime(2021, 3, 28, 2, 50).timetuple()) Out: 1616896200.0 In : time.mktime(datetime(2021, 3, 28, 3, 0).timetuple()) Out: 1616893200.0 In : time.mktime(datetime(2021, 3, 28, 3, 10).timetuple()) Out: 1616893800.0 I would very much appreciate your insight. I am not sure this is the right list to ask; apologies if it isn?t. Cheers. ES.Enrique -------------- next part -------------- An HTML attachment was scrubbed... URL: From evert.rol at gmail.com Thu Oct 14 06:02:21 2021 From: evert.rol at gmail.com (Evert Rol) Date: Thu, 14 Oct 2021 12:02:21 +0200 Subject: [AstroPy] datetime and timestamp In-Reply-To: <08AD8EEC-77D5-424C-9F8B-BAE87C131E0E@iaa.es> References: <08AD8EEC-77D5-424C-9F8B-BAE87C131E0E@iaa.es> Message-ID: <7EEE17C0-EE08-4376-B80C-CE68839C8EDF@gmail.com> That will be due to daylight savings: the difference between the second and third time is 3000 seconds, or 50 minutes, which is 1 hour (daylight savings) - 10 minutes (difference given). If you use utctimetuple(), you'll get what you want: In [24]: time.mktime(datetime(2021, 3, 28, 3, 00).utctimetuple()) - time.mktime(datetime(2021, 3, 28, 2, 50).utctimetuple()) Out[24]: 600.0 An alternative is to use the .timestamp() method of a datetime object, with a specific UTC timezone: In [33]: datetime(2021, 3, 28, 3, 00, tzinfo=timezone.utc).timestamp() - datetime(2021, 3, 28, 2, 50, tzinfo=timezone.utc).timestamp() Out[33]: 600.0 > On 14 Oct 2021, at 11:17, eperez wrote: > > I get an inconsistent result when translating datetime to timestamp: > A later date gives a lower timestamp: tehere is a jump backwards: > > > In : time.mktime(datetime(2021, 3, 28, 2, 40).timetuple()) > Out: 1616895600.0 > > In : time.mktime(datetime(2021, 3, 28, 2, 50).timetuple()) > Out: 1616896200.0 > > In : time.mktime(datetime(2021, 3, 28, 3, 0).timetuple()) > Out: 1616893200.0 > In : time.mktime(datetime(2021, 3, 28, 3, 10).timetuple()) > Out: 1616893800.0 > > > I would very much appreciate your insight. > > I am not sure this is the right list to ask; apologies if it isn?t. > > Cheers. > ES.Enrique > > _______________________________________________ > AstroPy mailing list > AstroPy at python.org > https://mail.python.org/mailman/listinfo/astropy -------------- next part -------------- An HTML attachment was scrubbed... URL: From evert.rol at gmail.com Thu Oct 14 06:17:19 2021 From: evert.rol at gmail.com (Evert Rol) Date: Thu, 14 Oct 2021 12:17:19 +0200 Subject: [AstroPy] Reading FITS uncompressed headers performance In-Reply-To: References: Message-ID: Bzip doesn't care about the file format: it compresses the whole file (and needs the complete file for that information). It probably divides things up in compressed blocks, but is not aware of FITS headers and the like, and such blocks will not adhere to the file structure. Possibly, `pyfits.open` can read and uncompress the relevant blocks for the first (primary) header and not uncompress anything further, but I'm not aware of that functionality. So as far as I'm aware, you can't do what you want: you'll need to uncompress the whole file first, before you can read just the primary header. What you probably want, is to just compress the data section of the FITS HDUs. For that, you'll need to save the file with pyfits, with the compression algorithm specified for each HDU. See https://docs.astropy.org/en/stable/io/fits/usage/unfamiliar.html#astropy-io-fits-compressedimagedata . The compressed algorithms are described at https://docs.astropy.org/en/stable/io/fits/api/images.html#astropy.io.fits.CompImageHDU . Be aware that some truncation happens with floating point data, as also described in the latter link. The advantage of this is that the header is also readable with other tools: it is just plain text (as normal for FITS), and it's only the data that is compressed. There may be some external tools that can do this easily for you from the command line (perhaps even some of the astropy tools), instead of having to script this yourself, but I don't know such tools. > On 14 Oct 2021, at 10:44, Ji?? N?dvorn?k wrote: > > Hi all, > > I am a little confused about the performance of astropy.io.fits when trying to open just the primary header of a compressed (.bz2) FITS file. The header is uncompressed plain text, correctly ended by the END tag. > > Is there some setting that I need to use to parse the header without needing to decompress the whole file? > > Thank you, > > Jiri N. > _______________________________________________ > AstroPy mailing list > AstroPy at python.org > https://mail.python.org/mailman/listinfo/astropy -------------- next part -------------- An HTML attachment was scrubbed... URL: From eperez at iaa.es Thu Oct 14 06:24:01 2021 From: eperez at iaa.es (eperez) Date: Thu, 14 Oct 2021 12:24:01 +0200 Subject: [AstroPy] datetime and timestamp In-Reply-To: <7EEE17C0-EE08-4376-B80C-CE68839C8EDF@gmail.com> References: <08AD8EEC-77D5-424C-9F8B-BAE87C131E0E@iaa.es> <7EEE17C0-EE08-4376-B80C-CE68839C8EDF@gmail.com> Message-ID: Thank you !! > El 14 oct 2021, a las 12:02, Evert Rol escribi?: > > That will be due to daylight savings: the difference between the second and third time is 3000 seconds, or 50 minutes, which is 1 hour (daylight savings) - 10 minutes (difference given). > > If you use utctimetuple(), you'll get what you want: > > In [24]: time.mktime(datetime(2021, 3, 28, 3, 00).utctimetuple()) - time.mktime(datetime(2021, 3, 28, 2, 50).utctimetuple()) > Out[24]: 600.0 > > > An alternative is to use the .timestamp() method of a datetime object, with a specific UTC timezone: > > In [33]: datetime(2021, 3, 28, 3, 00, tzinfo=timezone.utc).timestamp() - datetime(2021, 3, 28, 2, 50, tzinfo=timezone.utc).timestamp() > Out[33]: 600.0 > > >> On 14 Oct 2021, at 11:17, eperez > wrote: >> >> I get an inconsistent result when translating datetime to timestamp: >> A later date gives a lower timestamp: tehere is a jump backwards: >> >> >> In : time.mktime(datetime(2021, 3, 28, 2, 40).timetuple()) >> Out: 1616895600.0 >> >> In : time.mktime(datetime(2021, 3, 28, 2, 50).timetuple()) >> Out: 1616896200.0 >> >> In : time.mktime(datetime(2021, 3, 28, 3, 0).timetuple()) >> Out: 1616893200.0 >> In : time.mktime(datetime(2021, 3, 28, 3, 10).timetuple()) >> Out: 1616893800.0 >> >> >> I would very much appreciate your insight. >> >> I am not sure this is the right list to ask; apologies if it isn?t. >> >> Cheers. >> ES.Enrique >> >> _______________________________________________ >> 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: From nadvornik.ji at gmail.com Thu Oct 14 09:32:51 2021 From: nadvornik.ji at gmail.com (=?UTF-8?B?SmnFmcOtIE7DoWR2b3Juw61r?=) Date: Thu, 14 Oct 2021 15:32:51 +0200 Subject: [AstroPy] Reading FITS uncompressed headers performance In-Reply-To: References: Message-ID: Aha, so maybe I misunderstood how "less" works with the files - it displays the header correctly even for the .bz2 file. I thought it behaves so because the header is not compressed, only data is. I'm attaching the SDSS image FITS link to the .bz2 file so it's clear what I'm talking about. BR, Jiri ?t 14. 10. 2021 v 12:17 odes?latel Evert Rol napsal: > Bzip doesn't care about the file format: it compresses the whole file (and > needs the complete file for that information). It probably divides things > up in compressed blocks, but is not aware of FITS headers and the like, and > such blocks will not adhere to the file structure. Possibly, `pyfits.open` > can read and uncompress the relevant blocks for the first (primary) header > and not uncompress anything further, but I'm not aware of that > functionality. > So as far as I'm aware, you can't do what you want: you'll need to > uncompress the whole file first, before you can read just the primary > header. > > What you probably want, is to just compress the data section of the FITS > HDUs. For that, you'll need to save the file with pyfits, with the > compression algorithm specified for each HDU. See > https://docs.astropy.org/en/stable/io/fits/usage/unfamiliar.html#astropy-io-fits-compressedimagedata . > The compressed algorithms are described at > https://docs.astropy.org/en/stable/io/fits/api/images.html#astropy.io.fits.CompImageHDU . > Be aware that some truncation happens with floating point data, as also > described in the latter link. > > The advantage of this is that the header is also readable with other > tools: it is just plain text (as normal for FITS), and it's only the data > that is compressed. > > There may be some external tools that can do this easily for you from the > command line (perhaps even some of the astropy tools), instead of having to > script this yourself, but I don't know such tools. > > > > On 14 Oct 2021, at 10:44, Ji?? N?dvorn?k wrote: > > Hi all, > > I am a little confused about the performance of astropy.io.fits when > trying to open just the primary header of a compressed (.bz2) FITS file. > The header is uncompressed plain text, correctly ended by the END tag. > > Is there some setting that I need to use to parse the header without > needing to decompress the whole file? > > Thank you, > > Jiri N. > _______________________________________________ > 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: From yannick.roehlly at gmail.com Thu Oct 14 10:42:21 2021 From: yannick.roehlly at gmail.com (Yannick Roehlly) Date: Thu, 14 Oct 2021 16:42:21 +0200 Subject: [AstroPy] Reading FITS uncompressed headers performance In-Reply-To: References: Message-ID: Hi Ji??, You must have a ?eval "$(lessfile)"? or ?eval "$(lesspipe)"? somewhere in your shell configuration that will make less pre-process the files before displaying the content. If you do `head frame-u-001894-1-0103.fits.bz2` you will see that the file is actually compressed. Yannick From nadvornik.ji at gmail.com Thu Oct 14 11:20:38 2021 From: nadvornik.ji at gmail.com (=?UTF-8?B?SmnFmcOtIE7DoWR2b3Juw61r?=) Date: Thu, 14 Oct 2021 17:20:38 +0200 Subject: [AstroPy] Reading FITS uncompressed headers performance In-Reply-To: References: Message-ID: Thank you! ?t 14. 10. 2021 v 16:42 odes?latel Yannick Roehlly < yannick.roehlly at gmail.com> napsal: > Hi Ji??, > > You must have a ?eval "$(lessfile)"? or ?eval "$(lesspipe)"? somewhere > in your shell configuration that will make less pre-process the files > before displaying the content. If you do `head > frame-u-001894-1-0103.fits.bz2` you will see that the file is actually > compressed. > > Yannick > _______________________________________________ > AstroPy mailing list > AstroPy at python.org > https://mail.python.org/mailman/listinfo/astropy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimmyboysingh at gmail.com Mon Oct 18 07:12:27 2021 From: jimmyboysingh at gmail.com (Jim Singh) Date: Mon, 18 Oct 2021 22:12:27 +1100 Subject: [AstroPy] Some SIMBAD queries erroring? Message-ID: Hi all, Apologies in advance if I am missing something obvious, but sometimes the below (relatively straightforward) script returns a result set from SIMBAD, and sometimes errors with 'no element found'. Your assistance would be greatly appreciated. The script fetches co-ordinates for given planets and asteroids from JPL Horizons (which it successfully does for each one I've tried), and then asks SIMBAD to return objects within 1 degree radius of those co-ordinates. When it works, SIMBAD returns many records and the datatset make sense, but sometimes the aforementioned error occurs. This is the script: from astroquery.jplhorizons import Horizons from astroquery.simbad import Simbad import astropy.units as u from astropy.time import Time import astropy.coordinates as coord from astropy.coordinates import Angle observing_time = Time.strptime('2021-Oct-18 09:30:00', '%Y-%b-%d %H:%M:%S') #obj = Horizons(id="ceres", location=None, epochs=observing_time.jd) #The Simbad query for "ceres", "pallas", "vesta" fails, but id=199 returns a result obj = Horizons(id='599', id_type='majorbody', location=None, epochs=observing_time.jd) #The Simbad query for '599' and '699'fails, but '799' and '899' return a result #----Fetch RA and Dec of object from JPL Horizons----- eph = obj.ephemerides() CentreRA = eph['RA'][0] CentreDec = eph['DEC'][0] a=Angle(CentreRA, u.deg) CentreRAhms = (a.to_string(unit=u.hour)) b=Angle(CentreDec, u.deg) CentreDecdms = (b.to_string(unit=u.deg)) CoordStr = (CentreRAhms + " " + CentreDecdms) print(CoordStr) #----Query SIMBAD-------------- result = Simbad.query_region(coord.SkyCoord(CoordStr, frame='icrs'), radius='1d0m0s') print(result) Thanks for your help! Regards, Jim -------------- next part -------------- An HTML attachment was scrubbed... URL: From pdzwig at summaventures.com Mon Oct 18 08:50:13 2021 From: pdzwig at summaventures.com (Peter Dzwig) Date: Mon, 18 Oct 2021 13:50:13 +0100 Subject: [AstroPy] Fwd: YASQ - Yet Another SkyCoord Question In-Reply-To: References: Message-ID: <391e95ec-4a54-ba28-c9e1-780b55cd18dc@summaventures.com> Jim, FYI I had errors of a similar type, some while back and I got this from Andrew. Eventually I was able to get the detail in the end. But it does appear to be intermittent issues at Simbad's end. I think it got raised as a bug, but I don't know what the current status is. Peter -------- Forwarded Message -------- Subject: Re: [AstroPy] YASQ - Yet Another SkyCoord Question Date: Thu, 4 Feb 2021 15:23:23 -0500 From: Adrian Price-Whelan To: pdzwig at summaventures.com, Astronomical Python mailing list Hi Peter, It's possible that there are some intermittent issues with the Simbad database itself, or with your connection. I just tried and it worked for me: >>>?coord.SkyCoord.from_name("LEDA30866") Did the error message return any additional information? It's possible we need to audit the error messages we raise to make sure they provide enough information for cases like this. best, Adrian On Thu, Feb 4, 2021 at 3:14 PM Peter Dzwig > wrote: All, I have been attempting to get RA, Dec from SkyCoord via SkyCoord.from_name. It claims to be "unable to resolve" quite a few names. As a concrete example, LEDA 30866: SkyCoord.from_name(LEDA30866) oit goes to CDS at strasbourg and gives me back the message: "Unable to resolve", yet if I go directly to HyperLEDA (a) it is a recognised object (PGC030866); (b) it cross-identifies it and gives *three* SDSS names (plus others). If instead I put in one of the various SDSS names (I have tried all three) I get the same message. The obvious question: why can't it resolve the name? is it because it hasn't a way to choose between the choice names? Can someone clarify - and possibly offer a way to resolve this issue? So far I have encountered this issue in about 20% of my searches. Many thanks, Peter -- Dr. Peter Dzwig _______________________________________________ AstroPy mailing list AstroPy at python.org https://mail.python.org/mailman/listinfo/astropy -- Adrian M. Price-Whelan Flatiron Institute, NYC http://adrn.github.io (he / him) From adrianmpw at gmail.com Thu Oct 28 11:12:14 2021 From: adrianmpw at gmail.com (Adrian Price-Whelan) Date: Thu, 28 Oct 2021 11:12:14 -0400 Subject: [AstroPy] Astropy Coordination Committee 3 (CoCo3) Message-ID: Dear all, Following the conclusion of the election process, the new Astropy Coordinating Committee (CoCo3) has formed and has been meeting regularly on Thursdays. Running notes from the CoCo meetings are publicly viewable and can be found here: CoCo3 running notes . If you have any questions or would like to discuss anything in these notes, we encourage you to comment directly in the running notes doc, post to the #project channel on Slack, or send email to coordinators at astropy.org. One of the first actions taken by the new CoCo was to document the CoCo operating rules and policies. These can be viewed in CoCo Operating Policies . Our principal task as CoCo is to coordinate among the many contributors and project members that help the Astropy Project to function and to grow in many different roles (from coding the core package, to affiliate packages, tutorials, outreach, organization etc.). But Astropy is, as much as possible, a community-driven project where anyone can freely express their opinions, make suggestions, and decisions are driven by community consensus. With that in mind, the CoCo would like to propose a few role changes, and we expect to propose a few more in the coming months. While APE0 gives the responsibility to create and change roles to the CoCo, the CoCo welcomes individuals or groups to volunteer for and suggest new roles (indeed, the Release committee was a suggestion from a non-CoCo member; see https://www.astropy.org/team.html for the current roles). Hence, we would like to ask the community to nominate people (including self-nominations) for the following roles: - Affiliated package editor (please send suggestions to coordinators at astropy.org) - Finance committee member (please send suggestions to coordinators at astropy.org) - Astropy Release committee (look for an announcement from Tom Robitaille soon) - Astropy webpage maintainer (please send suggestions to coordinators at astropy.org) We will then follow the process for adding people to these roles . We always welcome ideas, feedback, or comments, so please start a thread in #project or reach out via coordinators at astropy.org if you would like to get in touch! - Adrian, on behalf of the Astropy Coordinating Committee: Matt Craig Kelle Cruz Moritz G?nther Adrian Price-Whelan Erik Tollerud -- Adrian M. Price-Whelan (he / him) Associate Research Scientist Center for Computational Astrophysics Flatiron Institute http://adrn.github.io -------------- next part -------------- An HTML attachment was scrubbed... URL: