Skip to content

Conversation

@JunyungKim
Copy link
Collaborator


Pull Request Description

What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)

#2489

What are the significant changes in functionality due to this change request?

For Change Control Board: Change Request Review

The following review must be completed by an authorized member of the Change Control Board.

  • 1. Review all computer code.
  • 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
  • 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
  • 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
  • 5. If significant functionality is added, there must be tests added to check this. Tests should cover all possible options. Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in XML block, the node <internalParallel> to True.
  • 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change. The requirements and the requirements test shall be in sync.
  • 7. The merge request must reference an issue. If the issue is closed, the issue close checklist shall be done.
  • 8. If an analytic test is changed/added is the the analytic documentation updated/added?
  • 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

@JunyungKim JunyungKim requested review from Jimmy-INL and wangcj05 May 5, 2025 16:03
@JunyungKim JunyungKim self-assigned this May 5, 2025
@moosebuild
Copy link

Job Test Ubuntu 20-2 Optional on 173e987 : invalidated by @joshua-cogliati-inl

restarted civet

Copy link
Contributor

@joshua-cogliati-inl joshua-cogliati-inl left a comment

Choose a reason for hiding this comment

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

Just a quick change request (I haven't done a full review). Thanks.

@moosebuild
Copy link

Job Test Ubuntu 18-2 Python 3 on 5c43f5a : invalidated by @joshua-cogliati-inl

cleaned computer filesystem so more room available

@joshua-cogliati-inl joshua-cogliati-inl dismissed their stale review May 12, 2025 15:56

The requested change was made.

Comment on lines 47 to 67
self.deltaH = 0.001 # set value for the change in height
self.deltaVol = 0.1 # volume fraction assumed to be the upper limit for the bed
self.slopeStop = self.deltaVol / self.deltaH # calculate the limit on the change in slope to determine bed height
self.dPart = 2.5e-4 # particle volume (m)
# particle diameter: d_p0(1) = 6.9e-4
# self.rTol = self.dPart / 1000 # tolerance for particle diameter
self.rTol = 2.e-3 # TODO read from MFIX input file d_p0(1) * 2
self.rHem = 0.0045 # radius of hemispherical section at the bottom of the cone
self.hOff = self.rHem / np.tan(np.pi / 6) # height of the cone at the bottom of the cone ( height of the hemispherical section)
self.nYMesh = 115
self.basePartFile = 'BACKGROUND_IC_*.vtp' # Polygonal data, 2D grid, like the unstructured grid, but there are no polyhedra, but only flat polygons.
self.cellPartFile = 'X_SLICE_*.vtu' # Unstructured grid: 2D or 3D grid; for every grid point all three coordinates and for each grid cell all constituent points and the cell shape are given
self.moveAgeWindow = 5
self.errTol = 0.0001
# self.heightBin = 0.01
self.numParticle = 3
self.heightBin = self.numParticle * self.dPart
self.coneRadius = 0.0254 #meters
self.coneHeight = 0.045 #meters
self.slantHeight = 0.0507204 # meters
self.cylinderAboveConeHeight = 0.17780 + self.coneHeight
Copy link
Collaborator

Choose a reason for hiding this comment

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

why all these geometrical hard coded variables/values?

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.

4 participants