Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reactor Module 2025 Training material updates #30071

Open
wants to merge 4 commits into
base: next
Choose a base branch
from

Conversation

aaronoaks
Copy link

Reason

Reactor Module training will be held in May 2025, material needs to be updated with latest features and best practices.

Design

Material is part of the Tutorial 4: Meshing

Impact

Updates to Meshing Tutorial content.

@aaronoaks aaronoaks changed the base branch from next to master March 10, 2025 20:36
@aaronoaks aaronoaks force-pushed the reactor-training-2025 branch from 0903477 to 20573f6 Compare March 10, 2025 20:40
@aaronoaks aaronoaks changed the base branch from master to next March 10, 2025 20:41
aaronoaks pushed a commit to aaronoaks/moose that referenced this pull request Mar 10, 2025
@aaronoaks aaronoaks force-pushed the reactor-training-2025 branch from 20573f6 to 047efd7 Compare March 10, 2025 20:46
@moosebuild
Copy link
Contributor

moosebuild commented Mar 10, 2025

Job Documentation, step Docs: sync website on 297e58d wanted to post the following:

View the site here

This comment will be updated on new commits.

@moosebuild
Copy link
Contributor

moosebuild commented Mar 11, 2025

Job Coverage, step Generate coverage on 297e58d wanted to post the following:

Framework coverage

Coverage did not change

Modules coverage

Coverage did not change

Full coverage reports

Reports

This comment will be updated on new commits.

@aaronoaks aaronoaks force-pushed the reactor-training-2025 branch from f41cf17 to 297e58d Compare March 13, 2025 16:47
@shikhar413
Copy link
Contributor

@eshemon in case you want to review what the reactor module tutorial documentation looks like with Yinbin and my changes incorporated, you can take a look at these temporary links:

@eshemon
Copy link
Contributor

eshemon commented Mar 13, 2025 via email

@loganharbour
Copy link
Member

[like] Shemon, Emily R. reacted to your message:

I think this is the first time I've seen an outlook reaction end up in a github comment 😆

@eshemon
Copy link
Contributor

eshemon commented Mar 13, 2025

@loganharbour I "liked it" on Outlook, then I thought to myself, "that probably didn't do anything, I'll log on to Github", then I saw it WORKED!

@aaronoaks
Copy link
Author

@loganharbour I noticed when looking through the slides that our old slides don't lay out the way I remember. The code blocks look to be larger font, and take up more space than before. E.g., in this slide below, the code block and figure used to be two 50/50 side by side, now the code block considerably overpowers the figure. If the presentation visual style has been updated since the last training, do you know if there are directives we area able to apply to revert the behavior for our presentation?

https://mooseframework.inl.gov/docs/PRs/30071/site/getting_started/examples_and_tutorials/tutorial04_meshing/presentation/index.html#/12/3

@aaronoaks
Copy link
Author

@loganharbour We also found while testing out of examples files on INL HPC that some of our test cases were producing input errors. We have corrections for these input files, but it doesn't look like CIVET noticed the issues. Are these test cases being exercised by CIVET, or is there something that needs to be updated to check them?

https://github.com/aaronoaks/moose/tree/reactor-training-2025/tutorials/tutorial04_meshing/app/test/tests/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants