16 APR Dev Session Notes

[tpike3]

Notes from 16 April Session let me know if I missed or misrepresented anything:

• Around the room to discuss what folks are working/ thinking about.

  • Mesa Visualization challenges, install and way forward : In order to update the javascript front end, the choice was made to download directly instead via npm. This make it easier for the user (who doesn't need to install npm) but places burden on the developers (who must update in multiple spaces) and make reproducibility harder. This is seen as a temporary fix with a long term fix developed in the context of the Mesa development strategy Mesa Strategy (draft) 21 April 2022 #1288. One recommended way forward is to create a separate repo Mesa-Visualization 0.1.0.
  • EOL 3.6: We need to signal Python 3.6 is no longer supported @jackiekazil plans to place in the release notes

• Review Quartzsite release Looking at the milestones my gut says many of these are addressed or partly addressed, but could be wrong.

  • PoC: Multiple-agent types scheduling and datacollection #1142 @EwoutH ? or transfer to @rht
  • CI: Python 3.6 should be removed because it has reached EOL #1165 @jackiekazil
  • Upgrade to Bootstrap 4! #1282 @tpike3 owes @rht a review
  • batch_run should default to running on 1 CPU #1210 @tpike3 (if no new contributor claims)

• Mesa-Geo update @wang-boyu

  • Continues to do great work and gave a shout out to @rht for his awesome support
  • @jackiekazil coordinate with @Corvince to release Mesa-Geo PyPI authority

• Establish May milestones

  • js: Update D3 from 4.13.0 to 7.4.3 #1270 @tpike3 needs to review (will also close Migrate D3 from v4 to v7 #1088)
  • Git tags out of sync with conda and PyPi (0.8.8 and 0.8.9 missing on git) #1076 @jackiekazil

• Discuss improvements to reach Mesa 1.0

  • Issues with the Grid implementation #808

[GaelLucero]

added pull request #1278 for discussion. Work previously presented in collaboration with @aiwhoo

[GaelLucero]

Made an additional commit (8a2b3fe) to pull request #1278 ready for further review and discussion

[aiwhoo]

I'm sorry to ask, but is the meeting 800est or 700est given the time zone differences and day light savings time?

[rht]

By comparing it with the other timezones listed, I think it is 8:00 EDT. We should just call it 8:00 ET.

[tpike3]

Oh dang I though it was the reverse (stupid daylight savings), however @rht's solution is much more elegant so updated

[wang-boyu]

@tpike3 you probably @ the wrong person with the same name as mine who also happens to be a PhD student lol

And I was wondering why there was no notification of being mentioned here : )

[tpike3]

Well crap...I have fixed... sorry about that

[wang-boyu]

No worries!

[Corvince]

@tpike3 Is it correct that you edited this thread to change it from the dev meeting announcement to the dev session notes? I didn't receive a notification for your edit and stumbled upon the notes rather accidently, because I was really looking forward to the notes.

I think in the future it would be better to instead comment the notes, because edits don't seem to cause notifications.

[tpike3]

@Corvince Good to know, thanks! In the future I will make the notes separate so there is a notification.