search

FormingWorlds / PROTEUS

Coupled atmosphere-interior framework to simulate the temporal evolution of rocky planets.
https://fwl-proteus.readthedocs.io
Apache License 2.0
11 stars 1 forks source link

Include warnings for user to update the code to modules latest versions #240

Open EmmaPostolec opened 1 hour ago

EmmaPostolec commented 1 hour ago

Hi, as I mentioned during the PROTEUS meeting this morning, proteus.py crashes when running the default configuration file: $ proteus start --config input/default.toml I 'git pulled' the main branch on my local computer to make sure I'm up to date, but it still crashes (see the proteus_00.log file attached for more details). The KeyError is "mass".

Let me know if you have any idea how to fix this :)

proteus_00.log

nichollsh commented 1 hour ago

Have you updated your Mors to the latest version? This could be related to some of the changes Laurent made last week.

EmmaPostolec commented 1 hour ago

Ah good point thanks @nichollsh ! I just did it and it works perfectly fine. I will think about it next time so I don't open a new issue for this. :)

nichollsh commented 1 hour ago

Glad this helped @EmmaPostolec! I had a similar problem too, so figured it might be the same thing. I wonder if it's possible to add a warning for the user if they haven't updated something.

EmmaPostolec commented 1 hour ago

Yes, it would definitely be useful to anyone working on the code (especially new users like Bsc or Msc students) I think !

EmmaPostolec commented 1 hour ago

Should I reopen this issue and suggest this idea as a code improvement ? @nichollsh

timlichtenberg commented 54 minutes ago

Yes, this seems like a good idea.

nichollsh commented 50 minutes ago

Another similar thing to do would be to print the module configuration to the log. This makes sure the user is aware of what they are using, and also is useful for knowing what configuration was used for a run.

EmmaPostolec commented 36 minutes ago

Nice ! So the goal would be to include warning for the user to update his code to the latest version of Proteus. One way to do it is first by printing the module configuration to the log file while running proteus.py as @nichollsh suggested.