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

Multiple Inputs for dummy models #2006

Merged
merged 4 commits into from
Nov 18, 2022
Merged

Conversation

mandd
Copy link
Collaborator

@mandd mandd commented Nov 9, 2022


Pull Request Description

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

close #2005

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.

@mandd mandd added priority_normal task This tag should be used for any new capability, improvement or enanchment labels Nov 9, 2022
@mandd mandd requested a review from wangcj05 November 9, 2022 21:47
@moosebuild
Copy link

Job Mingw Test on 8a75a8e : canceled by @joshua-cogliati-inl

needs to restart

@moosebuild
Copy link

Job Mingw Test on 8a75a8e : invalidated by @joshua-cogliati-inl

civet was slow

@moosebuild
Copy link

All jobs on 8a75a8e : invalidated by @wangcj05

Copy link
Collaborator

@wangcj05 wangcj05 left a comment

Choose a reason for hiding this comment

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

@mandd I have a comment for you to review.

Comment on lines -155 to -157
if len(myInput)>1:
self.raiseAnError(IOError,'Only one input is accepted by the model type '+self.type+' with name'+self.name)

Copy link
Collaborator

Choose a reason for hiding this comment

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

@mandd I guess we can remove this constraint for external model, but I think we still need it for ROM. Could you just remove this constraint in the external model.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Fixed

@wangcj05 wangcj05 added the RAVENv2.3 for RAVEN 2.3 Release label Nov 16, 2022
Copy link
Collaborator

@wangcj05 wangcj05 left a comment

Choose a reason for hiding this comment

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

I have some comments for you to consider.

Comment on lines 175 to 184
def _manipulateInput(self,dataIn):
"""
Method that is aimed to manipulate the input in order to return a common input understandable by this class
@ In, dataIn, object, the object that needs to be manipulated
@ Out, inRun, dict, the manipulated input
"""
if len(dataIn)>1:
self.raiseAnError(IOError,'Only one input is accepted by the model type '+self.type+' with name'+self.name)
inRun = super()._manipulateInput(dataIn)
return inRun
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think you can remove these lines. I think we only need to keep one check

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Fixed

Comment on lines 200 to 201
[(inputDict)],kwargs = super().createNewInput(myInput,samplerType,**kwargs)
return [(inputDict)],copy.deepcopy(kwargs)
Copy link
Collaborator

Choose a reason for hiding this comment

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

It seems a little bit redundant here, may be you can do:

     newInput, kwargs = super().createNewInput(myInput,samplerType,**kwargs)
     return newInput, kwargs

I think there is no need to do deep copy here, since the deep copy is handled in super class.

If you change the code, please also update the docstring.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

deepcopy removed, i kept the original format for consistency

Copy link
Collaborator

@wangcj05 wangcj05 left a comment

Choose a reason for hiding this comment

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

One additional comment @mandd

@@ -172,6 +172,35 @@ def applyRunInfo(self, runInfo):
"""
self.numThreads = runInfo.get('NumThreads', 1)

def _manipulateInput(self,dataIn):
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can you remove this method from the ROM class? I think it is not needed. @mandd
The check has been performed in createNewInput

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

good point, removed

Copy link
Collaborator

@wangcj05 wangcj05 left a comment

Choose a reason for hiding this comment

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

changes look good.

@wangcj05
Copy link
Collaborator

PR looks good, and checklist is satisfied.

@wangcj05 wangcj05 merged commit cfa775c into devel Nov 18, 2022
@wangcj05 wangcj05 deleted the mandd/externalModelMultpleInputs branch November 18, 2022 04:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority_normal RAVENv2.3 for RAVEN 2.3 Release task This tag should be used for any new capability, improvement or enanchment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[TASK] Multiple inputs for Dummy Model
3 participants