From rbaer25 at gmail.com Mon Apr 4 04:26:56 2022 From: rbaer25 at gmail.com (Rudolf Baer) Date: Mon, 4 Apr 2022 10:26:56 +0200 Subject: [AstroPy] astropy timeseries Gaia Message-ID: <8F33B1AB-289C-4719-8FFC-8082846A5F2F@gmail.com> I am trying to use the time series for light curves of Gaia DR2. The documentation shows only two formats: kepler.fits and tess.fits. The Gaia data light curve data are originally in csv format; via topcat I can save them in .fits or votable formats, and I can read and plot them without problems. However they do not work with timeseries. I show a partial screen shot of the format in topcat. The time is the Onboard time of Gaia. Any specific advice will be highly appreciated Rudolf Baer PS: Are there any plans to have specific gaia format? A mayor Gaia DR3 release will be on June 13, 2022 -------------- next part -------------- An HTML attachment was scrubbed... URL: From adrianmpw at gmail.com Mon Apr 4 16:05:41 2022 From: adrianmpw at gmail.com (Adrian Price-Whelan) Date: Mon, 4 Apr 2022 16:05:41 -0400 Subject: [AstroPy] astropy timeseries Gaia In-Reply-To: <8F33B1AB-289C-4719-8FFC-8082846A5F2F@gmail.com> References: <8F33B1AB-289C-4719-8FFC-8082846A5F2F@gmail.com> Message-ID: Hi Rudolf, I think it would be great to support reading Gaia data in astropy.timeseries! I have some questions about the implementation, but maybe we should move this discussion into a GitHub issue -- do you want to open an issue about this in the astropy repository? https://github.com/astropy/astropy/issues best, Adrian On Mon, Apr 4, 2022 at 4:27 AM Rudolf Baer wrote: > I am trying to use the time series for light curves of Gaia DR2. The > documentation shows only two formats: kepler.fits and tess.fits. > The Gaia data light curve data are originally in csv format; via topcat I > can save them in .fits or votable formats, and I can read and plot them > without problems. However they do not work with timeseries. I show a > partial screen shot of the format in topcat. The time is the Onboard time > of Gaia. > > [image: Screenshot 2022-04-03 at 11 42 17] > > > Any specific advice will be highly appreciated > Rudolf Baer > PS: Are there any plans to have specific gaia format? A mayor Gaia DR3 > release will be on June 13, 2022 > _______________________________________________ > AstroPy mailing list > AstroPy at python.org > https://mail.python.org/mailman/listinfo/astropy > -- 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: From rbaer25 at gmail.com Tue Apr 5 05:47:10 2022 From: rbaer25 at gmail.com (Rudolf Baer) Date: Tue, 5 Apr 2022 11:47:10 +0200 Subject: [AstroPy] astropy timeseries Gaia In-Reply-To: References: <8F33B1AB-289C-4719-8FFC-8082846A5F2F@gmail.com> Message-ID: Hi Adrian I have done it as suggested. Please have a look at it and let me know whether this is ok - I do not have a lot of experience with github. With best regards Rudolf On Mon, Apr 4, 2022 at 10:06 PM Adrian Price-Whelan wrote: > Hi Rudolf, > > I think it would be great to support reading Gaia data > in astropy.timeseries! > > I have some questions about the implementation, but maybe we should move > this discussion into a GitHub issue -- do you want to open an issue about > this in the astropy repository? > https://github.com/astropy/astropy/issues > > best, > Adrian > > > On Mon, Apr 4, 2022 at 4:27 AM Rudolf Baer wrote: > >> I am trying to use the time series for light curves of Gaia DR2. The >> documentation shows only two formats: kepler.fits and tess.fits. >> The Gaia data light curve data are originally in csv format; via topcat I >> can save them in .fits or votable formats, and I can read and plot them >> without problems. However they do not work with timeseries. I show a >> partial screen shot of the format in topcat. The time is the Onboard time >> of Gaia. >> >> [image: Screenshot 2022-04-03 at 11 42 17] >> >> >> Any specific advice will be highly appreciated >> Rudolf Baer >> PS: Are there any plans to have specific gaia format? A mayor Gaia DR3 >> release will be on June 13, 2022 >> _______________________________________________ >> AstroPy mailing list >> AstroPy at python.org >> https://mail.python.org/mailman/listinfo/astropy >> > > > -- > Adrian M. Price-Whelan (he / him) > Associate Research Scientist > Center for Computational Astrophysics > Flatiron Institute > http://adrn.github.io > _______________________________________________ > AstroPy mailing list > AstroPy at python.org > https://mail.python.org/mailman/listinfo/astropy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pdzwig at summaventures.com Tue Apr 5 12:32:32 2022 From: pdzwig at summaventures.com (Peter Dzwig) Date: Tue, 5 Apr 2022 17:32:32 +0100 Subject: [AstroPy] Noise region usage Message-ID: <7a77a99f-321d-de45-1188-84acea84a62e@summaventures.com> I am using correlation.template_correlate to compare a reference and an observed spectrum. In fact I am looking at a range which may contain several lines As I understand it I have to provide an uncertainty with the observed spectrum. I estimate it using noise_region_uncertainty. The docs say for noise_region_uncertainty: "Parameters spectrum Spectrum1D The spectrum to which we want to set the uncertainty. spectral_region SpectralRegion The region to use to calculate the standard deviation." Elsewhere on the Manipulation pages, under noise estimation it says to: "estimate the uncertainty from the region that does not contain the line" In other words use a sub-spectrum away from the areas of interest to estimate the noise. However when I do so I get an error indicating that the two samples aren't of the same length. Surely the noise estimation region should be "long enough" to get a decent estimate of the uncertainty, but there's no need for it to be the same length as the whole spectrum. An I correct or mis-reading the docs? Thanks -- Dr. Peter Dzwig From pdzwig at summaventures.com Sat Apr 23 11:18:55 2022 From: pdzwig at summaventures.com (Peter Dzwig) Date: Sat, 23 Apr 2022 16:18:55 +0100 Subject: [AstroPy] specutils.analysis.correlation Message-ID: <80e797cc-2551-77a5-65da-fd8d1035e2fd@summaventures.com> Can people clear up a few points for me on this. (i) Is specutils.analysis.correlation just scipy's correlation adapted to handle Spectrum1Ds; (ii) Does it require the two input spectra to have been resampled before input, or is *all* necessary resampling done internally; (iii) what technique is used for calculating the correlations? I am trying to compare this to another approach and I can't find sufficient detail in the docs for what I need. Many thanks, Peter -- Dr. Peter Dzwig From pdzwig at summaventures.com Sun Apr 24 06:13:36 2022 From: pdzwig at summaventures.com (Peter Dzwig) Date: Sun, 24 Apr 2022 11:13:36 +0100 Subject: [AstroPy] RECALL: specutils.analysis.correlation In-Reply-To: <80e797cc-2551-77a5-65da-fd8d1035e2fd@summaventures.com> References: <80e797cc-2551-77a5-65da-fd8d1035e2fd@summaventures.com> Message-ID: Please ignore last night's mail as the issues have most likely been resolved in the interim. Many thanks, Peter On 23/04/2022 16:18, Peter Dzwig wrote: > Can people clear up a few points for me on this. > > (i) Is specutils.analysis.correlation just scipy's correlation adapted > to handle Spectrum1Ds; > > (ii) Does it require the two input spectra to have been resampled before > input, or is *all* necessary resampling done internally; > > (iii) what technique is used for calculating the correlations? > > I am trying to compare this to another approach and I can't find > sufficient detail in the docs for what I need. > > Many thanks, > > Peter -- Dr. Peter Dzwig From simon at sconseil.fr Sat Apr 30 17:27:31 2022 From: simon at sconseil.fr (Simon Conseil) Date: Sat, 30 Apr 2022 23:27:31 +0200 Subject: [AstroPy] astropy v5.1rc1 ready for testing Message-ID: Hi everyone, The first release candidate (RC) of the core astropy package for the v5.1 release is now available and ready for testing! If you are interested in trying it out, you can install this release candidate by doing: pip install astropy --pre or pip install astropy==5.1rc1 You can find the documentation corresponding to this release at: https://docs.astropy.org/en/v5.1rc1/ including the full list of changes for this release: https://docs.astropy.org/en/v5.1.x/changelog.html as well as a 'What's new in v5.1?' page: https://docs.astropy.org/en/v5.1rc1/whatsnew/5.1.html We would appreciate if you could try out this RC and report back any success or failure via the following wiki page: https://github.com/astropy/astropy/wiki/v5.1-RC-testing For example, you can try running the test suite as mentioned on the wiki page. In addition, if you maintain any packages that use astropy, please check that your package(s) works well with this RC and let us know if there are any issues or whether everything works fine. There is a section to list packages that work/don't work at the bottom of the wiki page. Please also open an issue in the astropy core package issue tracker for any issues you encounter (and open separate issues for each problem you run into). If you use conda, be sure to either remove the existing conda astropy package or make a new environment before installing the RC. Note that there are no conda packages for the RC. Thanks! Simon (release manager for v5.1)