David Nicholson

Thank you @sdruskat and @jspaaks for your detailed replies. > Can I ask what you think where this information would be most helpful to provide, from your perspective as a...

Sure thing, thank you @jspaaks for going through all that effort. Yes, I agree with how you have outlined the options. Would be nice to have some support for different...

Good to know about, thank you @sdruskat. I am checking out the concept paper and will share it around. Do you think there could be a similar workflow to publish...

There's also a bit of a chicken-and-egg problem, that you must be aware of already. I can update the CITATION.cff metadata by hand or script, and then publish to Zenodo,...

Anyway: I don't mean to keep adding to your GitHub notifications. Please do let me know if there's something you want me to do to close this issue, or if...

I noticed when googling that there used to be a `{warning}` callout but it must have been removed at some point? From this page: https://myst-nb.readthedocs.io/en/v0.9.0/_sources/use/myst.md.txt ``` :::{warning} If you are...

meta-level summary of workshop from @cosden: https://us-rse.org/first-community-workshop/2022-05-13-workshop-summary/

Alternatively @exoticDFT wonders if "there is a specific Jekyll way to hide that one file from the event's page, but not the calendar"

I think we should just rename `Engine` and pass in `torch.Module` models. This feels like the most explicit API that best provides composability: there's an engine, it takes in models...

I think something like this will be necessary to achieve #472 without adding a ton of very specific logic to the `_eval` function Basically the `_eval` function should not have...