!DEkEPGCygOsVHrOCNQ:cadair.com

Python in Heliophysics

68 Members
A new room for collaborations in Python tools for all heliophysics http://heliopython.org14 Servers

Load older messages


Timestamp Message
6 Jan 2020
15:49:10@juliebarnum:matrix.orgJulie Barnum (LASP-CU)Yes
15:51:24@cadair:cadair.comCadairyay, for once my calendar isn't telling me lies
15:52:07@cadair:cadair.comCadairPlease can you share the zoom link in here when you get a moment?
16:01:38@namurphy:matrix.orgNick Murphyhttps://cuboulder.zoom.us/j/395871054
16:02:02@namurphy:matrix.orgNick MurphyJust starting the call now...
16:02:55@juliebarnum:matrix.orgJulie Barnum (LASP-CU)Zoom info Description:Topic: PyHC Zoom Meeting Time: This is a recurring meeting Meet anytime Join Zoom Meeting https://cuboulder.zoom.us/j/395871054 Meeting ID: 395 871 054 One tap mobile +16699006833,,395871054# US (San Jose) +16465588656,,395871054# US (New York) Dial by your location +1 669 900 6833 US (San Jose) +1 646 558 8656 US (New York) Meeting ID: 395 871 054 Find your local number: https://cuboulder.zoom.us/u/ab3XRN96S2 Join by SIP 395871054@zoomcrc.com Join by H.323 162.255.37.11 (US West) 162.255.36.11 (US East) 221.122.88.195 (China) 115.114.131.7 (India) 213.19.144.110 (EMEA) 103.122.166.55 (Australia) 209.9.211.110 (Hong Kong) 64.211.144.160 (Brazil) 69.174.57.160 (Canada) 207.226.132.110 (Japan) Meeting ID: 395 871 054
16:03:37@juliebarnum:matrix.orgJulie Barnum (LASP-CU)For future ref, I try to remember to always include the zoom info in my reminder emails, but also it's also available on the Google Calendar (in the info section for each telecon)
16:03:47@namurphy:matrix.orgNick MurphyHere's the link to the files that were changed for the PyHC standards document in the PR I created to implement what we talked about at the fall meeting: https://github.com/heliophysicsPy/standards/pull/16/files
16:04:08@cadair:cadair.comCadairI just have go digging in my email 😁
16:04:19@cadair:cadair.comCadairthat's the wildwest in there
16:04:26@juliebarnum:matrix.orgJulie Barnum (LASP-CU)I feel that!
17:30:17@namurphy:matrix.orgNick Murphy We just approved the pull request to update our standards document based on discussions at our meeting in November. If you would like to be added as a co-author, please let me know by responding on here or commenting on GitHub. It'd be helpful to know the name/affiliation/ORCID you would like used, in case it changed from the original document.
17:32:04@cadair:cadair.comCadair+1
17:32:23@cadair:cadair.comCadairI will be an author 🙂
18:08:55@wtbarnes:matrix.orgwtbarnes @room One last reminder: Applications for Python in Astronomy 2020 close TODAY! The conference will be held from 20 - 24 April 2020 at Trinity College, Dublin. You can apply here: https://forms.gle/mtdm6QKENdY8Y1Ph9. More information about the conference is available here: http://openastronomy.org/pyastro/2020/
7 Jan 2020
17:12:53@tomasangela:matrix.orgtomasangela joined the room.
8 Jan 2020
23:33:34@fritz:tchncs.defritz joined the room.
9 Jan 2020
15:51:56@hayesla:matrix.orghayesla set a profile picture.
23:04:37@namurphy:matrix.orgNick Murphy Is anyone interested in proposing a Python in Heliophysics session at this year's SHINE meeting in Honolulu from July 13-17? The session proposals are due next Friday, January 17. I probably won't be attending this year, so someone else would need to lead it. Here's the session proposal from 2019.
23:05:30@namurphy:matrix.orgNick MurphyI head back from Tulasi Parashar who is potentially interested in helping put together a proposal, but isn't sure if he will be able to go either.
23:21:13@wtbarnes:matrix.orgwtbarnesI won't be at SHINE this year so unlikely ☹️
23:23:31* @cadair:cadair.comCadair wishes someone would fly him to Hawaii
23:24:13@wtbarnes:matrix.orgwtbarnesSeems like they should at least let you see DKIST once...
23:27:53@namurphy:matrix.orgNick MurphyTulasi brought up the idea of a broader session on scientific reproducibility and open source science.
10 Jan 2020
20:47:27@abhijeetmanhas:openastronomy.orgastromanhas (@abhimanhas:openastronomy.org) joined the room.
23:20:59@niels:feneas.orgniels joined the room.
14 Jan 2020
16:56:29@johncoxon:matrix.orgjohncoxon joined the room.
21 Jan 2020
22:08:01@juliebarnum:matrix.orgJulie Barnum (LASP-CU)Hey all, as a reminder we decided at the last telecon to have another telecon this Friday, January 24th, at 10 AM MT. We don't have a topic yet set for the telecon. I went through the Fall 2019 meeting's notes and saw these lingering questions... any topic jump out at you all? Perhaps someone has another topic in their mind to discuss? :)
22:08:06@juliebarnum:matrix.orgJulie Barnum (LASP-CU)

PyHc Telecon Ideas

  • Add mission statement, goals, roles to heliopython website (are all of these defined?)
  • Coordinating committee might still be nice, to help make decisions. What kind of decisions will we need to make? Do we need a formal decision-making structure? We’ve been on a loose-consensus basis lately. A representative democracy might still be nice.
  • By the next meeting in the spring, aim to have all packages on the website reviewed. Will we have someone hired by then? If not, how should we handle this?
  • General direction of the group in 2020? Did we have a hard set idea of where we want to take this group and steps to get there?
22:10:21@juliebarnum:matrix.orgJulie Barnum (LASP-CU) *

PyHc Telecon Ideas

  • Add mission statement, goals, roles to heliopython website (are all of these defined?)
  • Coordinating committee might still be nice, to help make decisions. What kind of decisions will we need to make? Do we need a formal decision-making structure? We’ve been on a loose-consensus basis lately. A representative democracy might still be nice.
  • By the next meeting in the spring, aim to have all packages on the website reviewed. Will we have someone hired by then? If not, how should we handle this?
  • General direction of the group in 2020? Did we have a hard set idea of where we want to take this group and steps to get there?

There are no newer messages yet.


Back to Room List