From astropy at liska.ath.cx Thu Sep 7 09:47:15 2017 From: astropy at liska.ath.cx (Ole Streicher) Date: Thu, 07 Sep 2017 15:47:15 +0200 Subject: [AstroPy] Creating file-like object from HDUList? Message-ID: Hi, I have a rather large HDUList that was creating from a memory mapped fits file by using slices on its data array(s): from astropy.io import fits hdul0 = fits.open('datacube.fits', memmap = True) // >> 1GB hdul1 = fits.HDUList([ fits.PrimaryHDU(header = hdul0[0].header), fits.ImageHDU(data = hdul0[1].data[:100, :100, :100], header = hdul0[1].header)]) Is it now possible to create a file-like object opened in read mode without needing to read everything beforehand? Like here: res = io.BytesIO() hdul1.writeto(res) send_file(res, mime_type="application/fits") but without creating a large in-memory object with res, and without temporary storage on disk? Best regards Ole From t.r.marsh at warwick.ac.uk Fri Sep 8 05:54:28 2017 From: t.r.marsh at warwick.ac.uk (Thomas Marsh) Date: Fri, 8 Sep 2017 10:54:28 +0100 Subject: [AstroPy] Modelling with weights Message-ID: Hello, I am interested in using astropy.modeling. Am I right in thinking that in the case of least squares, the usual inverse variance weights for chi**2 minimisation would be obtained by setting weights = 1/(standard deviation) rather than 1/(variance)? (I deduced this from the code for LevMarLSQFitter and my understanding of scipy.optimize.leastsq) Cheers, Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From jvmirca at gmail.com Fri Sep 8 11:57:27 2017 From: jvmirca at gmail.com (=?UTF-8?B?WsOpIFZpbsOtY2l1cw==?=) Date: Fri, 8 Sep 2017 08:57:27 -0700 Subject: [AstroPy] Modelling with weights In-Reply-To: References: Message-ID: Hi Tom, Yes, you are right, the "standard" chi ** 2 minimization is obtained by setting weights = 1 / std. However, note that if weights is uniformly constant, i.e., weights[i] = c, for all i, c different than 0, then its value doesn't matter as far as optimization is concerned. Best, Z? On Fri, Sep 8, 2017 at 2:54 AM, Thomas Marsh wrote: > Hello, > > > I am interested in using astropy.modeling. Am I right in thinking that in > the case of least squares, the usual inverse variance weights for chi**2 > minimisation would be obtained by setting weights = 1/(standard deviation) > rather than 1/(variance)? (I deduced this from the code for LevMarLSQFitter > and my understanding of scipy.optimize.leastsq) > > > Cheers, > > > Tom > > _______________________________________________ > AstroPy mailing list > AstroPy at python.org > https://mail.python.org/mailman/listinfo/astropy > > -- github: @mirca twitter: @mircaze webpage: mirca.github.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From dnfarias at uc.cl Fri Sep 8 15:01:54 2017 From: dnfarias at uc.cl (Diego Farias) Date: Fri, 8 Sep 2017 16:01:54 -0300 Subject: [AstroPy] astropy.convolution.convolve Message-ID: Hi everyone, I have an issue with astropy.convolution.convolve on astropy version 1.3.3; I'm just doing astropy_conv = convolve([1, 4, 5, 6, 5, 7, 8], [0.2, 0.6, 0.2]) TypeError: 'bool' object is not callable Cheers, Diego -------------- next part -------------- An HTML attachment was scrubbed... URL: From evert.rol at gmail.com Fri Sep 8 15:08:56 2017 From: evert.rol at gmail.com (Evert Rol) Date: Fri, 8 Sep 2017 21:08:56 +0200 Subject: [AstroPy] astropy.convolution.convolve In-Reply-To: References: Message-ID: <25F1701B-F10D-4776-A385-298F01801241@gmail.com> > I have an issue with astropy.convolution.convolve on astropy version 1.3.3; I'm just doing > > astropy_conv = convolve([1, 4, 5, 6, 5, 7, 8], [0.2, 0.6, 0.2]) > TypeError: 'bool' object is not callable It's hard to see without the code before it, but it looks like `convolve` is a bool. You probably have an assignment somewhere like `convolve = True` earlier in your code. From sic at elte.hu Fri Sep 8 15:29:17 2017 From: sic at elte.hu (Brigitta Sipocz) Date: Fri, 8 Sep 2017 20:29:17 +0100 Subject: [AstroPy] astropy.convolution.convolve In-Reply-To: <25F1701B-F10D-4776-A385-298F01801241@gmail.com> References: <25F1701B-F10D-4776-A385-298F01801241@gmail.com> Message-ID: Hi Diego, While I agree with Evert, that it would be much easier to help if you would show a full failing example, I would also strongly encourage you to update your astropy version, as significant changes were made in the convolution module for the 2.0 release: http://docs.astropy.org/en/latest/whatsnew/2.0.html#whatsnew-2-0-convolution Cheers, Brigitta On 8 September 2017 at 20:08, Evert Rol wrote: > > I have an issue with astropy.convolution.convolve on astropy version > 1.3.3; I'm just doing > > > > astropy_conv = convolve([1, 4, 5, 6, 5, 7, 8], [0.2, 0.6, 0.2]) > > TypeError: 'bool' object is not callable > > It's hard to see without the code before it, but it looks like `convolve` > is a bool. > You probably have an assignment somewhere like `convolve = True` earlier > in your code. > > _______________________________________________ > AstroPy mailing list > AstroPy at python.org > https://mail.python.org/mailman/listinfo/astropy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dnfarias at uc.cl Sat Sep 9 12:33:07 2017 From: dnfarias at uc.cl (Diego Farias) Date: Sat, 9 Sep 2017 13:33:07 -0300 Subject: [AstroPy] AstroPy Digest, Vol 132, Issue 3 In-Reply-To: References: Message-ID: You were right. It is a long code so I didn't realiza that there was a boolean convolve. Thanks a lot! Cheers, Diego On Sep 9, 2017 1:03 PM, wrote: > Send AstroPy mailing list submissions to > astropy at python.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.python.org/mailman/listinfo/astropy > or, via email, send a message with subject or body 'help' to > astropy-request at python.org > > You can reach the person managing the list at > astropy-owner at python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of AstroPy digest..." > > > Today's Topics: > > 1. astropy.convolution.convolve (Diego Farias) > 2. Re: astropy.convolution.convolve (Evert Rol) > 3. Re: astropy.convolution.convolve (Brigitta Sipocz) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 8 Sep 2017 16:01:54 -0300 > From: Diego Farias > To: astropy at python.org > Subject: [AstroPy] astropy.convolution.convolve > Message-ID: > mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi everyone, > > I have an issue with astropy.convolution.convolve on astropy version 1.3.3; > I'm just doing > > astropy_conv = convolve([1, 4, 5, 6, 5, 7, 8], [0.2, 0.6, 0.2]) > TypeError: 'bool' object is not callable > > Cheers, > > Diego > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: 20170908/8431cab7/attachment-0001.html> > > ------------------------------ > > Message: 2 > Date: Fri, 8 Sep 2017 21:08:56 +0200 > From: Evert Rol > To: Astronomical Python mailing list > Subject: Re: [AstroPy] astropy.convolution.convolve > Message-ID: <25F1701B-F10D-4776-A385-298F01801241 at gmail.com> > Content-Type: text/plain; charset=us-ascii > > > I have an issue with astropy.convolution.convolve on astropy version > 1.3.3; I'm just doing > > > > astropy_conv = convolve([1, 4, 5, 6, 5, 7, 8], [0.2, 0.6, 0.2]) > > TypeError: 'bool' object is not callable > > It's hard to see without the code before it, but it looks like `convolve` > is a bool. > You probably have an assignment somewhere like `convolve = True` earlier > in your code. > > > > ------------------------------ > > Message: 3 > Date: Fri, 8 Sep 2017 20:29:17 +0100 > From: Brigitta Sipocz > To: Astronomical Python mailing list > Subject: Re: [AstroPy] astropy.convolution.convolve > Message-ID: > gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi Diego, > > While I agree with Evert, that it would be much easier to help if you would > show a full failing example, I would also strongly encourage you to update > your astropy version, as significant changes were made in the convolution > module for the 2.0 release: > http://docs.astropy.org/en/latest/whatsnew/2.0.html# > whatsnew-2-0-convolution > > Cheers, > Brigitta > > On 8 September 2017 at 20:08, Evert Rol wrote: > > > > I have an issue with astropy.convolution.convolve on astropy version > > 1.3.3; I'm just doing > > > > > > astropy_conv = convolve([1, 4, 5, 6, 5, 7, 8], [0.2, 0.6, 0.2]) > > > TypeError: 'bool' object is not callable > > > > It's hard to see without the code before it, but it looks like `convolve` > > is a bool. > > You probably have an assignment somewhere like `convolve = True` earlier > > in your code. > > > > _______________________________________________ > > AstroPy mailing list > > AstroPy at python.org > > https://mail.python.org/mailman/listinfo/astropy > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: 20170908/a593287e/attachment-0001.html> > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > AstroPy mailing list > AstroPy at python.org > https://mail.python.org/mailman/listinfo/astropy > > > ------------------------------ > > End of AstroPy Digest, Vol 132, Issue 3 > *************************************** > -------------- next part -------------- An HTML attachment was scrubbed... URL: From petr at kubanek.net Sun Sep 10 07:34:20 2017 From: petr at kubanek.net (Petr =?ISO-8859-1?Q?Kub=E1nek?=) Date: Sun, 10 Sep 2017 13:34:20 +0200 Subject: [AstroPy] Ephemeris calculation Message-ID: <1505043260.22450.5.camel@kubanek.net> Hi, I am looking for Python package, to download ephemeris from MPEC (see below for an example; no, I am not looking for propagation of one line MPEC, I really need to interpolate from ephemeris provided by MPEC) and calculate RA DEC for given time (+sky motion will be excellent, but of course I can live without it). Any idea? I understand MPEC webcgi will not work for scripts, but copy&paste will. Or anything else? I am just lazy to write a parser..can of course do that, but I don't want to reinvent the wheel. Thanks Petr Kub?nek http://rts2.org 00243 [H= 9.94] Date UT R.A. (J2000) Decl. Delta r El. Ph. V Sky Motion Uncertainty info h m s "/min P.A. 3-sig/" P.A. 2017 09 10 000000 12 43 00.8 -05 24 35 3.810 2.927 24.8 8.3 15.8 0.96 113.1 N/A N/A / Map / Offsets 2017 09 11 000000 12 44 25.9 -05 33 36 3.816 2.927 24.2 8.1 15.7 0.96 113.1 N/A N/A / Map / Offsets 2017 09 12 000000 12 45 51.2 -05 42 38 3.822 2.927 23.6 7.9 15.7 0.96 113.0 N/A N/A / Map / Offsets 2017 09 13 000000 12 47 16.6 -05 51 40 3.827 2.928 23.0 7.7 15.7 0.96 113.0 N/A N/A / Map / Offsets 2017 09 14 000000 12 48 42.2 -06 00 42 3.833 2.928 22.4 7.5 15.7 0.96 113.0 N/A N/A / Map / Offsets 2017 09 15 000000 12 50 08.0 -06 09 44 3.838 2.928 21.8 7.3 15.7 0.97 112.9 N/A N/A / Map / Offsets 2017 09 16 000000 12 51 34.0 -06 18 47 3.843 2.929 21.2 7.1 15.7 0.97 112.9 N/A N/A / Map / Offsets 2017 09 17 000000 12 53 00.1 -06 27 49 3.848 2.929 20.7 7.0 15.7 0.97 112.9 N/A N/A / Map / Offsets 2017 09 18 000000 12 54 26.3 -06 36 51 3.853 2.929 20.1 6.8 15.7 0.97 112.8 N/A N/A / Map / Offsets 2017 09 19 000000 12 55 52.8 -06 45 53 3.858 2.930 19.5 6.6 15.7 0.97 112.8 N/A N/A / Map / Offsets 2017 09 20 000000 12 57 19.3 -06 54 55 3.862 2.930 18.9 6.4 15.7 0.97 112.8 N/A N/A / Map / Offsets 2017 09 21 000000 12 58 46.1 -07 03 57 3.867 2.930 18.3 6.2 15.7 0.97 112.7 N/A N/A / Map / Offsets 2017 09 22 000000 13 00 12.9 -07 12 58 3.871 2.931 17.7 6.0 15.7 0.97 112.7 N/A N/A / Map / Offsets 2017 09 23 000000 13 01 39.9 -07 21 59 3.875 2.931 17.1 5.8 15.7 0.98 112.7 N/A N/A / Map / Offsets 2017 09 24 000000 13 03 07.1 -07 31 00 3.879 2.931 16.5 5.6 15.7 0.98 112.6 N/A N/A / Map / Offsets 2017 09 25 000000 13 04 34.4 -07 40 01 3.883 2.932 15.9 5.4 15.7 0.98 112.6 N/A N/A / Map / Offsets 2017 09 26 000000 13 06 01.9 -07 49 01 3.887 2.932 15.4 5.2 15.7 0.98 112.5 N/A N/A / Map / Offsets 2017 09 27 000000 13 07 29.4 -07 58 00 3.890 2.932 14.8 5.0 15.6 0.98 112.5 N/A N/A / Map / Offsets 2017 09 28 000000 13 08 57.1 -08 07 00 3.894 2.933 14.2 4.8 15.6 0.98 112.5 N/A N/A / Map / Offsets 2017 09 29 000000 13 10 25.0 -08 15 58 3.897 2.933 13.6 4.6 15.6 0.98 112.4 N/A N/A / Map / Offsets 2017 09 30 000000 13 11 52.9 -08 24 56 3.900 2.933 13.0 4.4 15.6 0.98 112.4 N/A N/A / Map / Offsets From petr at kubanek.net Sun Sep 10 13:11:36 2017 From: petr at kubanek.net (Petr =?ISO-8859-1?Q?Kub=E1nek?=) Date: Sun, 10 Sep 2017 19:11:36 +0200 Subject: [AstroPy] Ephemeris calculation In-Reply-To: <1505043260.22450.5.camel@kubanek.net> References: <1505043260.22450.5.camel@kubanek.net> Message-ID: <1505063496.22450.9.camel@kubanek.net> Hi all, I wrote the library. It's mostly trivial, yet might be handy - should't we include it in astropy? Source: https://github.com/RTS2/rts2/blob/master/python/rts2/mpcephem.py Checks: https://github.com/RTS2/rts2/blob/master/checks/check_python_mpcephem +check data: https://github.com/RTS2/rts2/blob/master/checks/data/mpecephem_ida I know it does not parse the header and assumes Sky speed/PA format, but I will work on this. Petr Petr Kub?nek p??e v Ne 10. 09. 2017 v 13:34 +0200: > Hi, > > I am looking for Python package, to download ephemeris from MPEC (see > below for an example; no, I am not looking for propagation of one > line > MPEC, I really need to interpolate from ephemeris provided by MPEC) > and > calculate RA DEC for given time (+sky motion will be excellent, but > of > course I can live without it). > > Any idea? I understand MPEC webcgi will not work for scripts, but > copy&paste will. Or anything else? I am just lazy to write a > parser..can of course do that, but I don't want to reinvent the > wheel. > > Thanks > > Petr Kub?nek > http://rts2.org > > 00243??????????????[H= 9.94] > Date???????UT??????R.A. (J2000) > Decl.????Delta?????r?????El.????Ph.???V??????Sky > Motion???????Uncertainty info > ????????????h m > s????????????????????????????????????????????????????????????"/min??? > ?P.A.????3-sig/" P.A. > 2017 09 10 000000 12 43 00.8 -05 24 > 35???3.810???2.927???24.8???8.3??15.8????0.96????113.1???????N/A???N/ > A / Map / Offsets > 2017 09 11 000000 12 44 25.9 -05 33 > 36???3.816???2.927???24.2???8.1??15.7????0.96????113.1???????N/A???N/ > A / Map / Offsets > 2017 09 12 000000 12 45 51.2 -05 42 > 38???3.822???2.927???23.6???7.9??15.7????0.96????113.0???????N/A???N/ > A / Map / Offsets > 2017 09 13 000000 12 47 16.6 -05 51 > 40???3.827???2.928???23.0???7.7??15.7????0.96????113.0???????N/A???N/ > A / Map / Offsets > 2017 09 14 000000 12 48 42.2 -06 00 > 42???3.833???2.928???22.4???7.5??15.7????0.96????113.0???????N/A???N/ > A / Map / Offsets > 2017 09 15 000000 12 50 08.0 -06 09 > 44???3.838???2.928???21.8???7.3??15.7????0.97????112.9???????N/A???N/ > A / Map / Offsets > 2017 09 16 000000 12 51 34.0 -06 18 > 47???3.843???2.929???21.2???7.1??15.7????0.97????112.9???????N/A???N/ > A / Map / Offsets > 2017 09 17 000000 12 53 00.1 -06 27 > 49???3.848???2.929???20.7???7.0??15.7????0.97????112.9???????N/A???N/ > A / Map / Offsets > 2017 09 18 000000 12 54 26.3 -06 36 > 51???3.853???2.929???20.1???6.8??15.7????0.97????112.8???????N/A???N/ > A / Map / Offsets > 2017 09 19 000000 12 55 52.8 -06 45 > 53???3.858???2.930???19.5???6.6??15.7????0.97????112.8???????N/A???N/ > A / Map / Offsets > 2017 09 20 000000 12 57 19.3 -06 54 > 55???3.862???2.930???18.9???6.4??15.7????0.97????112.8???????N/A???N/ > A / Map / Offsets > 2017 09 21 000000 12 58 46.1 -07 03 > 57???3.867???2.930???18.3???6.2??15.7????0.97????112.7???????N/A???N/ > A / Map / Offsets > 2017 09 22 000000 13 00 12.9 -07 12 > 58???3.871???2.931???17.7???6.0??15.7????0.97????112.7???????N/A???N/ > A / Map / Offsets > 2017 09 23 000000 13 01 39.9 -07 21 > 59???3.875???2.931???17.1???5.8??15.7????0.98????112.7???????N/A???N/ > A / Map / Offsets > 2017 09 24 000000 13 03 07.1 -07 31 > 00???3.879???2.931???16.5???5.6??15.7????0.98????112.6???????N/A???N/ > A / Map / Offsets > 2017 09 25 000000 13 04 34.4 -07 40 > 01???3.883???2.932???15.9???5.4??15.7????0.98????112.6???????N/A???N/ > A / Map / Offsets > 2017 09 26 000000 13 06 01.9 -07 49 > 01???3.887???2.932???15.4???5.2??15.7????0.98????112.5???????N/A???N/ > A / Map / Offsets > 2017 09 27 000000 13 07 29.4 -07 58 > 00???3.890???2.932???14.8???5.0??15.6????0.98????112.5???????N/A???N/ > A / Map / Offsets > 2017 09 28 000000 13 08 57.1 -08 07 > 00???3.894???2.933???14.2???4.8??15.6????0.98????112.5???????N/A???N/ > A / Map / Offsets > 2017 09 29 000000 13 10 25.0 -08 15 > 58???3.897???2.933???13.6???4.6??15.6????0.98????112.4???????N/A???N/ > A / Map / Offsets > 2017 09 30 000000 13 11 52.9 -08 24 > 56???3.900???2.933???13.0???4.4??15.6????0.98????112.4???????N/A???N/ > A / Map / Offsets > _______________________________________________ > AstroPy mailing list > AstroPy at python.org > https://mail.python.org/mailman/listinfo/astropy From raphael.attie at nasa.gov Mon Sep 11 13:41:26 2017 From: raphael.attie at nasa.gov (Attie, Raphael (GSFC-6710)[UNIVERSITIES SPACE RESEARCH ASSOCIATION]) Date: Mon, 11 Sep 2017 17:41:26 +0000 Subject: [AstroPy] memmap for RICE-compressed 3D fits? Message-ID: <144E1376-DE71-4B15-A6A7-3E17A6323F29@nasa.gov> Hello, As a regular users of large RICE-compressed 3D fits files, I have to get the 2D-slices in them. These 3D fits files are time series of images from SDO. The ones i?m using are typically [700 MB - 2 GB], with ZCMPTYPE= ?RICE_1 ?, XTENSION=?BINTABLE?, and keep the extension .fits (not .fits.gz or alike). I would like to use memory mapping so I do not need to load the whole cube before accessing a 2D frame. I used to do it in C with CFITSIO, with custom mex function for Matlab. It was working fine but I?m now transitioning to Python. With astropy.fits.open(), I see the option of using memmap = true. I never tried this option before on uncompressed 3D fits but using it on RICE-compressed 3D cube does not seem to make any difference with respect to the default (memmap = false). I test that by simply looking at the RAM usage of the python processes in each case. For reproducing the issue, I provide the codes and link to the data down below. So my questions are: 1) Is memory mapping supported for such RICE-compressed 3D fits files? 2) If it is supported, could my code down below loading the data misusing astropy.fits? 3) If it is not supported, what are the alternatives to do it within Python? Python code for loading the 1st slice of the data cube: from astropy.io import fits hdu = fits.open(file, ignore_missing_end=True, memmap=True) hdu.verify('silentfix') slice = hdu[1].data[1, :, :] Dropbox link to the 3D FITS file (also accessible to non-dropbox users): https://www.dropbox.com/s/t0se5aum5hwyvff/mtrack_20101126_170034_TAI_20101127_170034_TAI_LambertCylindrical_continuum.fits?dl=0 Thank you for your help, Raphael - - - - - - - - - -- - - - -- - - - -- - - - -- - - - -- - Dr. Raphael Atti? (GSFC-6710) NASA Postdoctoral fellow (NPP) NASA/Goddard Space Flight Center Universities Space Research Association Office 041: 301-286-0360 Cell: 301-631-4954 Email: raphael.attie at nasa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: From nimitbhardwaj at gmail.com Wed Sep 13 10:22:47 2017 From: nimitbhardwaj at gmail.com (Nimit Bhardwaj) Date: Wed, 13 Sep 2017 19:52:47 +0530 Subject: [AstroPy] Start for contribution Message-ID: Hello, I am Nimit Bhardwaj of Nit Hamirpur, India CSE 3rd year, I want to start contributing in the Astropy project, I know python very well, I want to ask what should I do to start contribution, like what should I learn, like the other concepts in physics, I only know the basic physics in the gravitation. Please guide me. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jvmirca at gmail.com Wed Sep 13 12:56:23 2017 From: jvmirca at gmail.com (=?UTF-8?B?WsOpIFZpbsOtY2l1cw==?=) Date: Wed, 13 Sep 2017 09:56:23 -0700 Subject: [AstroPy] Start for contribution In-Reply-To: References: Message-ID: Hi Nimit, That's great you want to contribute to AstroPy! Most of astropy's code contributions happen on GitHub: https://www.github.com/astropy/astropy Therefore, before anything else, I strongly recommend you to take a deep look at the AstroPy's development workflow: http://docs.astropy.org/en/stable/development/workflow/development_workflow.html This serves as a thorough guide for both very beginners and advanced contributors and it's applicable not only to astropy, but to basically every project that uses git as its version control system. If you are already acquainted with git and GitHub, I suggest you to take an overview of the code base to see what mostly attracts your interest. Besides, you might want to take a look at issues labeled as "package-novice" ( https://github.com/astropy/astropy/issues?q=is%3Aopen+is%3Aissue+label%3APackage-novice). Usually, those are easier to solve, which may help you to get familiar with the contribution workflow. Another big part of the AstroPy community is the affiliated packages. I'm not gonna get into details on this, but affiliated packages are basically like any other project, except they focus on more specialized features and tools (everything build on top of astropy). You can check out a list of those here: http://www.astropy.org/affiliated. Also, don't forget to take a look at the astropy documention: http://docs.astropy.org/en/stable/ Have a nice coding =) On Wed, Sep 13, 2017 at 7:22 AM, Nimit Bhardwaj wrote: > Hello, I am Nimit Bhardwaj of Nit Hamirpur, India CSE 3rd year, I want to > start contributing in the Astropy project, I know python very well, I want > to ask what should I do to start contribution, like what should I learn, > like the other concepts in physics, I only know the basic physics in the > gravitation. > > Please guide me. > > _______________________________________________ > AstroPy mailing list > AstroPy at python.org > https://mail.python.org/mailman/listinfo/astropy > > -- github: @mirca twitter: @mircaze webpage: mirca.github.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From nimitbhardwaj at gmail.com Wed Sep 13 15:37:07 2017 From: nimitbhardwaj at gmail.com (Nimit Bhardwaj) Date: Thu, 14 Sep 2017 01:07:07 +0530 Subject: [AstroPy] Start for contribution In-Reply-To: References: Message-ID: OK, thanks, I was reading the docs of the project, thanks On Wed, Sep 13, 2017 at 10:26 PM, Z? Vin?cius wrote: > Hi Nimit, > > That's great you want to contribute to AstroPy! > > Most of astropy's code contributions happen on GitHub: > https://www.github.com/astropy/astropy > > Therefore, before anything else, I strongly recommend you to take a deep > look at the AstroPy's development workflow: http://docs.astropy.org/en/ > stable/development/workflow/development_workflow.html > > This serves as a thorough guide for both very beginners and advanced > contributors and it's applicable not only to astropy, but to basically > every project that uses git as its version control system. > > If you are already acquainted with git and GitHub, I suggest you to take > an overview of the code base to see what mostly attracts your interest. > Besides, you might want to take a look at issues labeled as > "package-novice" (https://github.com/astropy/ > astropy/issues?q=is%3Aopen+is%3Aissue+label%3APackage-novice). Usually, > those are easier to solve, which may help you to get familiar with the > contribution workflow. > > Another big part of the AstroPy community is the affiliated packages. I'm > not gonna get into details on this, but affiliated packages are basically > like any other project, except they focus on more specialized features and > tools (everything build on top of astropy). You can check out a list of > those here: http://www.astropy.org/affiliated. > > Also, don't forget to take a look at the astropy documention: http://docs. > astropy.org/en/stable/ > > Have a nice coding =) > > On Wed, Sep 13, 2017 at 7:22 AM, Nimit Bhardwaj > wrote: > >> Hello, I am Nimit Bhardwaj of Nit Hamirpur, India CSE 3rd year, I want to >> start contributing in the Astropy project, I know python very well, I want >> to ask what should I do to start contribution, like what should I learn, >> like the other concepts in physics, I only know the basic physics in the >> gravitation. >> >> Please guide me. >> >> _______________________________________________ >> AstroPy mailing list >> AstroPy at python.org >> https://mail.python.org/mailman/listinfo/astropy >> >> > > > -- > github: @mirca > twitter: @mircaze > webpage: mirca.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 baweaver at lbl.gov Fri Sep 15 14:57:32 2017 From: baweaver at lbl.gov (Benjamin Alan Weaver) Date: Fri, 15 Sep 2017 11:57:32 -0700 Subject: [AstroPy] Creating file-like object from HDUList? In-Reply-To: References: Message-ID: Hello y'all, I'd be interested in an answer to this question as well. Kia ora koutou, Benjamin Alan Weaver On Thu, Sep 7, 2017 at 6:47 AM, Ole Streicher wrote: > Hi, > > I have a rather large HDUList that was creating from a memory mapped > fits file by using slices on its data array(s): > > from astropy.io import fits > > hdul0 = fits.open('datacube.fits', memmap = True) // >> 1GB > hdul1 = fits.HDUList([ fits.PrimaryHDU(header = hdul0[0].header), > fits.ImageHDU(data = hdul0[1].data[:100, :100, > :100], > header = hdul0[1].header)]) > > Is it now possible to create a file-like object opened in read mode without > needing to read everything beforehand? Like here: > > res = io.BytesIO() > hdul1.writeto(res) > send_file(res, mime_type="application/fits") > > but without creating a large in-memory object with res, and without > temporary storage on disk? > > Best regards > > Ole > > _______________________________________________ > AstroPy mailing list > AstroPy at python.org > https://mail.python.org/mailman/listinfo/astropy > -- With great responsibility seldom comes great power. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcraig at mnstate.edu Mon Sep 18 16:06:45 2017 From: mcraig at mnstate.edu (Matthew Craig) Date: Mon, 18 Sep 2017 20:06:45 +0000 Subject: [AstroPy] Python in Astronomy 2018 Message-ID: Hello all, The 2018 Python in Astronomy conference will be held on 30th Apr - 4th May 2018 at the Center for Computational Astrophysics at the Flatiron Institute in New York, New York. For more information see http://openastronomy.org/pyastro/2018/. Python in Astronomy 2018 aims to bring a wide variety of people who currently use, develop or teach people about Python packages in the context of all forms of Astronomy. The conference will include presentations, tutorials, unconference sessions, and sprints. As well as building the community around astronomical uses of Python, the conference aims to improve collaboration and interoperability between Python packages and share knowledge on Python packages and techniques. It will also provide training and educational materials for users and developers of Python packages. Participant selection will be made with the goal of enhancing the Python in Astronomy community and we particularly encourage requests to attend from junior astronomers and people who are new to contributing to open source software. Effort will also be made to select participants who have a demonstrated potential to contribute meaningfully to the Python in Astronomy infrastructure via providing educational materials, documentation, and/or coding. This conference is intended to be neither an introduction to Python bootcamp nor only for expert-level Python developers. If you are interested in attending and/or have any questions about the conference, please use this form: https://goo.gl/forms/47eYzrWsKPqIPTL42 Further, please nominate people who you think should might benefit from attending and contributing to Python in Astronomy 2018 using this form: https://goo.gl/forms/47eYzrWsKPqIPTL42 Applications from interested participants will open by Oct 16, 2017; the link to the application form will be available at the conference web site, http://openastronomy.org/pyastro/2018/ Matt Craig On behalf of the 2018 SOC: Azalee Bostroem Daniela Huppenkothen Andrew Leonard Duncan Macleod Brigitta Sipocz Erik Tollerud -------------- next part -------------- An HTML attachment was scrubbed... URL: From baweaver at lbl.gov Tue Sep 19 16:29:01 2017 From: baweaver at lbl.gov (Benjamin Alan Weaver) Date: Tue, 19 Sep 2017 13:29:01 -0700 Subject: [AstroPy] PyDL v0.6.0 released Message-ID: Hello y'all, PyDL v0.6.0 has been released. This is release is primarily to fully support Astropy >= 2.0. See http://pydl.readthedocs. io/en/stable/pydl/changes.html for details. This version of PyDL is *not* intended to be compatible with Astropy < 2.0. If you are still using older versions of Astropy, you can continue to use PyDL v0.5.4. There no significant changes in the API between 0.5.4 & 0.6.0. PyDL is available at https://pypi.python.org/pypi/pydl Kia ora koutou, Benjamin Alan Weaver -- With great responsibility seldom comes great power. -------------- next part -------------- An HTML attachment was scrubbed... URL: From npross at roe.ac.uk Wed Sep 20 15:16:26 2017 From: npross at roe.ac.uk (Nicholas Ross) Date: Wed, 20 Sep 2017 19:16:26 +0000 Subject: [AstroPy] Putting matplotib hexbin into an Aitoff projection In-Reply-To: References: Message-ID: <98287E70-C3F2-449A-9E6C-CFC0BCA840C3@roe.ac.uk> Dear All, I?m having a really hard time here, just wanting to put a matplotib hexbin into an Aitoff projection. There code and details are here:: https://stackoverflow.com/questions/46320712/putting-matplotib-hexbin-into-an-aitoff-projection Any and all thoughts, suggestions and comments, would more than welcome. Thanks, Nic ==================================== Dr. Nicholas P. Ross STFC Ernest Rutherford Fellow Institute for Astronomy University of Edinburgh Royal Observatory, Blackford Hill Edinburgh EH9 3HJ, United Kingdom +44 (0)131-668 8351 www.roe.ac.uk/~npross/ github.com/d80b2t/ ==================================== From kellecruz at gmail.com Mon Sep 25 12:36:35 2017 From: kellecruz at gmail.com (Kelle Cruz) Date: Mon, 25 Sep 2017 12:36:35 -0400 Subject: [AstroPy] Putting matplotib hexbin into an Aitoff projection In-Reply-To: <98287E70-C3F2-449A-9E6C-CFC0BCA840C3@roe.ac.uk> References: <98287E70-C3F2-449A-9E6C-CFC0BCA840C3@roe.ac.uk> Message-ID: Just to follow up on this, it looks like Nic?s question got a couple responses on StackOverflow (Thanks Evert!) which give some insight into matplotlib + Aitoff?s projections: https://stackoverflow.com/questions/46320712/putting- matplotib-hexbin-into-an-aitoff-projection (For the record, the tone of the responses by ImportanceofBeingEarnest are not in the spirit of the Astropy Project?s Code of Conduct. Indeed, they are actually great examples of tone which should be avoided in order to foster a welcoming and supportive community.) Kelle On Wed, Sep 20, 2017 at 3:16 PM, Nicholas Ross wrote: > Dear All, > > I?m having a really hard time here, just wanting to put a matplotib hexbin > into an Aitoff projection. > There code and details are here:: > https://stackoverflow.com/questions/46320712/putting- > matplotib-hexbin-into-an-aitoff-projection > Any and all thoughts, suggestions and comments, would more than welcome. > > Thanks, > Nic > > > ==================================== > Dr. Nicholas P. Ross > STFC Ernest Rutherford Fellow > Institute for Astronomy > University of Edinburgh > Royal Observatory, Blackford Hill > Edinburgh EH9 3HJ, United Kingdom > +44 (0)131-668 8351 > www.roe.ac.uk/~npross/ > github.com/d80b2t/ > ==================================== > > > > > _______________________________________________ > AstroPy mailing list > AstroPy at python.org > https://mail.python.org/mailman/listinfo/astropy > -- Kelle Cruz, PhD ? http://kellecruz.com/ 917.725.1334 ? Hunter: x16486 ? AMNH: x7930 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kellecruz at gmail.com Mon Sep 25 13:39:09 2017 From: kellecruz at gmail.com (Kelle Cruz) Date: Mon, 25 Sep 2017 13:39:09 -0400 Subject: [AstroPy] Creating file-like object from HDUList? In-Reply-To: References: Message-ID: Hi Ole and Benjamin, We discussed this question at the recent Coordination Meeting and the short answer is ?we don?t have a solution at the moment?. However, the general consensus is that this question would be worth posting in the Python in Astronomy Facebook group, which has many members (>2,500) and is quite active: https://www.facebook.com/groups/astropython/ Ole, if you don?t Facebook, would you mind if I posted it? (And if y?all have a sec, please consider checking to see if any of your colleagues/FB friends have requested to join ? current members can approve join requests of their friends. And if you need someone added, please send me an email directly or a FB message with their FB username.) Kelle On Fri, Sep 15, 2017 at 2:57 PM, Benjamin Alan Weaver wrote: > Hello y'all, > > I'd be interested in an answer to this question as well. > > Kia ora koutou, > Benjamin Alan Weaver > > On Thu, Sep 7, 2017 at 6:47 AM, Ole Streicher > wrote: > >> Hi, >> >> I have a rather large HDUList that was creating from a memory mapped >> fits file by using slices on its data array(s): >> >> from astropy.io import fits >> >> hdul0 = fits.open('datacube.fits', memmap = True) // >> 1GB >> hdul1 = fits.HDUList([ fits.PrimaryHDU(header = hdul0[0].header), >> fits.ImageHDU(data = hdul0[1].data[:100, :100, >> :100], >> header = hdul0[1].header)]) >> >> Is it now possible to create a file-like object opened in read mode >> without >> needing to read everything beforehand? Like here: >> >> res = io.BytesIO() >> hdul1.writeto(res) >> send_file(res, mime_type="application/fits") >> >> but without creating a large in-memory object with res, and without >> temporary storage on disk? >> >> Best regards >> >> Ole >> >> _______________________________________________ >> AstroPy mailing list >> AstroPy at python.org >> https://mail.python.org/mailman/listinfo/astropy >> > > > > -- > With great responsibility seldom comes great power. > > _______________________________________________ > AstroPy mailing list > AstroPy at python.org > https://mail.python.org/mailman/listinfo/astropy > > -- Kelle Cruz, PhD ? http://kellecruz.com/ 917.725.1334 ? Hunter: x16486 ? AMNH: x7930 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kellecruz at gmail.com Tue Sep 26 13:27:04 2017 From: kellecruz at gmail.com (Kelle Cruz) Date: Tue, 26 Sep 2017 17:27:04 +0000 Subject: [AstroPy] =?utf-8?q?Fwd=3A_=5BNumFOCUS_Projects=5D_Please_spread?= =?utf-8?q?_the_word=3A_Applications_now_open_for_DISC_Inaugural_Un?= =?utf-8?q?conference_=E2=80=94_Nov=2E_29-30_=40_PyDataNYC?= In-Reply-To: References: Message-ID: Hi All, Interested in working on making open source projects like Astropy and yt as inclusive as possible? Please consider applying for this unconference to be held in NYC Nov 29-30. It would be great to have a critical mass of folks from the astro community so that we can work on being change makers together! And critical mass of junior folks would be good, but even better would be to have some more senior white men participate as well. Kelle ---------- Forwarded message --------- From: Gina Helfrich Date: Thu, Sep 21, 2017 at 3:40 PM Subject: [NumFOCUS Projects] Please spread the word: Applications now open for DISC Inaugural Unconference ? Nov. 29-30 @ PyDataNYC To: Applications are open for the inaugural DISC Unconference Diversity & Inclusion in Scientific Computing to be held at PyData NYC , Nov. 29-30, 2017 We are looking for participants who want to be *change-makers*, whether or not they self-identify as part of an underrepresented group. The DISC Unconference mission is to equip participants to take action to help create a more *diverse and inclusive* open source scientific computing community. *Apply now* or *visit the website* for more information. *Please help us spread the word!* -- kelle (via iOS) -------------- next part -------------- An HTML attachment was scrubbed... URL: