Replies: 5 comments 5 replies
-
Reminder Mesa Dev Session this Saturday 7 January |
Beta Was this translation helpful? Give feedback.
-
I was really looking forward to this dev session but unfortunately I won’t be able to take part. Since I’m back from vacation, i still have quite high fever today and my ability of formulating consistent and useful thoughts and talking about them is strongly reduced. Anyways, one part I would be interested in as one possible outputs of this session is, how you intend to work on Mesa-Replay until you decide its API now is stable enough and it has the desired improvements (such as more optimized cache size). Do you intend to create a fork of the repo, work on it and once it is far enough, manually copy the code into the main mesa repo, or do you have another idea? |
Beta Was this translation helpful? Give feedback.
-
We had a lot to talk about... I forgot to add discussion about permission patterns (from last month). We should add this to next month. |
Beta Was this translation helpful? Give feedback.
-
7 January NotesIntegrating New Functionality, specifically Mesa - Replay by @LogendeBackground: When presenting results, computation can hinder ABMs, caching results so one can replay the model can be a highly effective approach to overcome this. @Logende built a great library to start addressing this challenge. The question for Project Mesa is how to keep momentum on such efforts and try and continue to improve them as it is a non-trivial challenge. The Dev Team agreed this functionality should be part of Core Mesa (i.e. main mesa repo) but needs to be developed more, as this is a very non-trivial problem. Way Ahead:
Mesa DevelopmentDev team decided improvements to space.py (grid) is major change for Mesa 2.0; However, many changes can be made for a Mesa 1.2 release. The goal is Mesa 1.2 released at next Dev Session 4 Februrary
Additional Issues
As always please feel free to correct or comment so we can make sure the notes are accurate. Next Dev Session 4 February |
Beta Was this translation helpful? Give feedback.
-
We have two Mesa papers. Currently writing an update paper. My concern
about JOSS would be that it would cause confusion… but that also might put
a line in the sand as the ultimate paper.
Let me consider it for a week or two.
…On Wed, Jan 18, 2023 at 3:15 PM Felix Neubauer ***@***.***> wrote:
@tpike3 <https://github.com/tpike3> Apologies, we have not attempted to
publish in JOSS before and it looks like we need to let mesa-replay bake
some more. I think I somehow got the wrong impression like some medical
journals you could do a short write-up of emerging concepts.
As the goal is to get the word out I will see if there is a more
appropriate venue and make sure it is included in the news letters. Again
apologies for the confusion.
Okay, yeah that makes sense.
I would assume that Mesa itself would be ready for JOSS though, if someone
would have the time to write the corresponding paper.
—
Reply to this email directly, view it on GitHub
<#1553 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABIWTXW3OONTP76IMHHYMLWTBFMXANCNFSM6AAAAAASX75G2U>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
When: 7 January --- 2000 UTC+8/1300 CET/1200 GMT/0700 EDT
Where: via Matrix
Proposed Agenda:
@jackiekazil @rht @Corvince @wang-boyu @Tortar @aiwhoo @nunezco2 @EwoutH @Logende Please feel free to add or takeaway from this agenda
Beta Was this translation helpful? Give feedback.
All reactions