19 Aug 2020 |
@wtbarnes:matrix.org | Wow this is great! | 16:49:36 |
@wtbarnes:matrix.org | I will try to look at this soon and give feedback and add some things as well. I've not had as much to give to this I'd like and I'm not sure that I'll be at the meeting this week, but we should probably all have a telecon soonish (maybe early next week?) to gather our thoughts with enough time to get something together before the deadline | 16:52:15 |
| @wtbarnes:matrix.org changed the room topic to "Discussion of white paper on software standards and support for the Heliophysics 2050 Workshop. See this Google Doc: https://docs.google.com/document/d/1I9dfyZpiZ80aesRYLisvJrk4pS1jAjuzG4U00JfjtgY/edit?usp=sharing" from "Discussion of white paper on software standards and support for the Heliophysics 2050 Workshop". | 16:53:00 |
| @wtbarnes:matrix.org changed the room topic to "Discussion of white paper on software standards and support for the Heliophysics 2050 Workshop. https://docs.google.com/document/d/1I9dfyZpiZ80aesRYLisvJrk4pS1jAjuzG4U00JfjtgY/edit?usp=sharing" from "Discussion of white paper on software standards and support for the Heliophysics 2050 Workshop. See this Google Doc: https://docs.google.com/document/d/1I9dfyZpiZ80aesRYLisvJrk4pS1jAjuzG4U00JfjtgY/edit?usp=sharing". | 16:53:48 |
| @wtbarnes:matrix.org changed the room topic to "https://docs.google.com/document/d/1I9dfyZpiZ80aesRYLisvJrk4pS1jAjuzG4U00JfjtgY/edit?usp=sharing" from "Discussion of white paper on software standards and support for the Heliophysics 2050 Workshop. https://docs.google.com/document/d/1I9dfyZpiZ80aesRYLisvJrk4pS1jAjuzG4U00JfjtgY/edit?usp=sharing". | 16:54:10 |
1 Sep 2020 |
| Nick Murphy joined the room. | 15:31:51 |
| wafels joined the room. | 15:40:01 |
| @dstansby:matrix.org joined the room. | 17:37:44 |
| jklenzing joined the room. | 20:03:22 |
2 Sep 2020 |
| @smithara:matrix.org joined the room. | 12:16:14 |
@smithara:matrix.org | Hiya - I am wondering if you are open to some input around interfacing with Earth sciences (e.g. geomagnetism, atmospheric stuff...). I have only vague ideas at the moment, but basically the premise is that there is heliophysics software/data that needs to interface better with other research communities (and organisations). The pathway to that is not clear. (as an example, GIC prediction needing input from solar monitoring to regional geology and power networks, and everything in between)
If it sounds relevant then I can try put something together (along the lines of - encouraging separate communities to adopt compatible principles, practices, and tools; providing space for developers to spend time between communities to build the connections needed; ...)?
| 12:56:53 |
@wtbarnes:matrix.org | I think that's a very good point! | 14:22:15 |
@wtbarnes:matrix.org | Obviously since we only have three pages, we're limited on how much we can say and we of course want the main focus to be heliophysics because of the nature of the call, but interfacing with other communities, and especially researchers within other divisions at NASA, is very important | 14:23:26 |
@wtbarnes:matrix.org | and if the current state of our software development practices impedes that, I think that's important to note | 14:23:54 |
@smithara:matrix.org | Ok understood - I'll add a small comment to the document about this. I guess it need only be a couple of lines alongside some relevant section. If it provokes discussion then I could look into contributing more | 14:35:05 |
@wtbarnes:matrix.org | 👍️ | 15:59:14 |
4 Sep 2020 |
@dstansby:matrix.org | another thought that popped into my head is that current python software development relies heavily on 'free' hosting and continuous integration services. I think it would be worth recommending in the long run that NASA provide these services for the community, or make allowance for paying for these services in grants/funding | 10:43:33 |
@wtbarnes:matrix.org | That's a really good point. And that certainly extends beyond Python too | 17:47:56 |
@wtbarnes:matrix.org | We actually are running into this problem with aiapy right now as we're exceeding the number of CI/CD minutes in the free tier and I was actually just wondering whether mission funding could be used to pay for something like that. | 17:48:51 |
9 Sep 2020 |
@wtbarnes:matrix.org | In reply to @smithara:matrix.org Ok understood - I'll add a small comment to the document about this. I guess it need only be a couple of lines alongside some relevant section. If it provokes discussion then I could look into contributing more I still have your text in the paper and I think it is a good point in support of providing an interoperable software ecosystem (i.e. it more easily enables cross-disciplinary research). Would you like to be added as a coauthor? | 07:07:13 |
16 Sep 2020 |
@smithara:matrix.org | Sorry I didn't see your reply! I haven't quite got my notifications for Element sorted.
Anyway thanks for adding me as a coauthor :)
Though having just read through the current text, I don't see my words in there, so do feel free to remove me! | 11:34:25 |
12 Jul 2021 |
| @dstansby:matrix.org left the room. | 09:39:30 |
15 Jul 2021 |
| @wtbarnes:matrix.org removed their profile picture. | 15:11:49 |
21 Oct 2021 |
| @wtbarnes:matrix.org left the room. | 13:49:41 |
18 Apr 2022 |
| @wybpip:matrix.org joined the room. | 13:08:54 |
| @wybpip:matrix.org left the room. | 13:08:54 |
2 May 2022 |
| @wybpip:matrix.org joined the room. | 01:13:50 |
| @wybpip:matrix.org left the room. | 01:13:51 |
25 Jun 2022 |
| @better_sleeping:converser.eu joined the room. | 21:24:06 |
| @better_sleeping:converser.eu left the room. | 21:24:13 |