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

Updating Doc String: Address Issue #258 #263

Open
wants to merge 8 commits into
base: devel
Choose a base branch
from

Conversation

csdechant
Copy link
Collaborator

This PR updates the Zapdos header files to include previously missing Doc String, which will close Issue #258. This PR also includes minor edits that remove previously unused parameters in Zapdos objects.

Updating the docstings in Zapdos is in progress with the following objects completed:
- Actions
- Auxkernels
- bcs
- constraits
- indicators
- interfacekernels
- postprocessors
- userobjects
Also minor edits of head and body files were done, which involved removing out dated parameters
@csdechant
Copy link
Collaborator Author

csdechant commented Nov 13, 2024

The PR for updating Zapdos Doc Sting is ready for review. @gsgall is the primary reviewer, but I included @cticenhour in case he would like to look at this PR too.

@moosebuild
Copy link
Collaborator

moosebuild commented Nov 13, 2024

Job Documentation, step Sync to remote on fb79626 wanted to post the following:

View the site here

This comment will be updated on new commits.

Copy link
Collaborator

@gsgall gsgall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall looks good, a few typos and some missing documentation, and lack of detail in comments but thank you for doing this @csdechant.

/*
* Helper function that supplies the Kernels for drift-diffusion for the electrons,
* energy independent charged particles, neutral particles, and
* electron mean energy depending
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sentence seems incomplete. Is this suppose to be mean electron energy dependent particles?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should read "electron mean energy density". Will edit.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This has been addressed in 4b5a202

virtual void addADKernels(const std::string & name,
const std::string & potential_name,
const bool & Using_offset,
const bool & charged,
const bool & energy);

/// Helper function that supplies the Aux kernels to convert scaled position units
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What are the scaled position units in this case referring to? Is this for when the user is using a non-dimensioqnalized spatial domain?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is correct. For clarity, I can add edit to:
/// Helper function that supplies the Aux kernels to convert scaled position units when parameter position_units is set to non-unity

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This has been addressed in 4b5a202

include/actions/AddPeriodicControllers.h Outdated Show resolved Hide resolved
Real _period;
/// The number of cycles to calculate the difference
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This description is unclear to me. Can you add some more detail here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, a probably better description is "The number of cycles PeriodicRelativeNodalDifference is active"

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This has been addressed in 4b5a202

include/auxkernels/AbsValueAux.h Outdated Show resolved Hide resolved
include/materials/GasBase.h Outdated Show resolved Hide resolved
include/userobjects/ProvideMobility.h Outdated Show resolved Hide resolved
@@ -56,13 +56,12 @@ AddPeriodicRelativeNodalDifference::validParams()
params.addParam<Real>(
"starting_cycle", 0.0, "The number of the cycles before starting the difference calculation");
params.addRequiredParam<Real>("cycle_frequency", "The cycle's frequency in Hz");
params.addParam<Real>(
"num_cycles", 2000.0, "The number of cycles to calculation the difference for.");
params.addParam<Real>("num_cycles", 2000.0, "The number of cycles to calculate the difference.");
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a bit unclear to me. Does this mean the number of cycles for which the difference between the current and previous cycle is calculated. Or is this something like the number of cycles between cycles that are being compared?

Copy link
Collaborator Author

@csdechant csdechant Dec 20, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is the former description. I can edit it to simply say "The number of cycles this object is active".

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This has been addressed in 4b5a202

src/interfacekernels/InterfaceAdvection.C Outdated Show resolved Hide resolved
Comment on lines 40 to 64

/*
* Helper function that supplies the Kernels for drift-diffusion for the electrons,
* energy independent charged particles, neutral particles, and
* electron mean energy depending
*/
virtual void addADKernels(const std::string & name,
const std::string & potential_name,
const bool & Using_offset,
const bool & charged,
const bool & energy);

/// Helper function that supplies the Aux kernels to convert scaled position units
virtual void addPosition(const std::string & position_name, const int & component);

/// Helper function that supplies the Aux kernels to convert densities from log form
virtual void addDensityLog(const std::string & particle_name);

/// Helper function that supplies the Aux kernels for current
virtual void addCurrent(const std::string & particle_name, const std::string & potential_name);

/// Helper function that supplies the Aux kernels for the electric field
virtual void addEfield(const std::string & Efield_name,
const std::string & potential_name,
const int & component);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cticenhour correct me if I am wrong but I believe the MOOSE standard should be to have a description for each of the parameters of every custom function. In the style of

@param name description

This comment is also applicable for the rest of the actions that do not have the parameter doc strings for their internal functions.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is true for most MOOSE header files I have seen and should add them regardless for better documentation. This was an oversight and will edit.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This has been addressed in 4b5a202

Co-authored-by: Grayson Gall <66559200+gsgall@users.noreply.github.com>
@moosebuild
Copy link
Collaborator

Job Precheck, step Clang format on 6a94f37 wanted to post the following:

Your code requires style changes.

A patch was auto generated and copied here
You can directly apply the patch by running, in the top level of your repository:

curl -s https://mooseframework.inl.gov/zapdos/docs/PRs/263/clang_format/style.patch | git apply -v

Alternatively, with your repository up to date and in the top level of your repository:

git clang-format e547cd7f514bbdef43d1cb1cba59e3ef02aa5be8

@csdechant
Copy link
Collaborator Author

@gsgall everything should be addressed now, and this PR is ready for a re-review.

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.

3 participants