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

Grid Sampler Crashed with Integer Grids #973

Closed
10 tasks done
wangcj05 opened this issue Apr 30, 2019 · 1 comment · Fixed by #1008
Closed
10 tasks done

Grid Sampler Crashed with Integer Grids #973

wangcj05 opened this issue Apr 30, 2019 · 1 comment · Fixed by #1008

Comments

@wangcj05
Copy link
Collaborator

wangcj05 commented Apr 30, 2019


Issue Description

What did you expect to see happen?

Raven should run without crash

What did you see instead?

Crashed and the pdf generation complains the type.

jianw@lemhi1 stationary_cracks]$ cat raven_qsub.e73554
which: no conda in (/apps/moose/stack/mvapich-2.3.1_gcc-8.2.0/bin:/apps/moose/stack/gcc-8.2.0/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/opt/pbs/bin:/opt/dell/srvadmin/bin)
/home/jianw/projects/raven/framework/contrib/cloudpickle/cloudpickle.py:47: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
  import imp
/home/jianw/.conda/envs/raven_libraries/lib/python3.6/site-packages/statsmodels/compat/pandas.py:56: FutureWarning: The pandas.core.datetools module is deprecated and will be removed in a future version. Please use the pandas.tseries module instead.
  from pandas.core import datetools
Traceback (most recent call last):
  File "/home/jianw/projects/raven/framework/Driver.py", line 285, in <module>
    raven()
  File "/home/jianw/projects/raven/framework/Driver.py", line 238, in raven
    simulation.run()
  File "/home/jianw/projects/raven/framework/Simulation.py", line 780, in run
    stepInstance.takeAstep(stepInputDict)
  File "/home/jianw/projects/raven/framework/Steps.py", line 312, in takeAstep
    self._initializeStep(inDictionary)
  File "/home/jianw/projects/raven/framework/Steps.py", line 242, in _initializeStep
    self._localInitializeStep(inDictionary)
  File "/home/jianw/projects/raven/framework/Steps.py", line 606, in _localInitializeStep
    newInput = self._findANewInputToRun(inDictionary[self.samplerType], inDictionary['Model'], inDictionary['Input'], inDictionary['Output'])
  File "/home/jianw/projects/raven/framework/Steps.py", line 722, in _findANewInputToRun
    found,newInp = sampler.generateInput(model,inputs)
  File "/home/jianw/projects/raven/framework/Samplers/Sampler.py", line 804, in generateInput
    self.localGenerateInput(model,oldInput)
  File "/home/jianw/projects/raven/framework/Samplers/Grid.py", line 205, in localGenerateInput
    self.inputInfo['SampledVarsPb'][key] = self.distDict[varName].pdf(self.values[key])
  File "/home/jianw/projects/raven/framework/Distributions.py", line 414, in pdf
    returnPdf = self._distribution.pdf(x)
  File "/home/jianw/projects/raven/crow/install/crow_modules/distribution1Dpy3.py", line 466, in pdf
    return _distribution1Dpy3.BasicUniformDistribution_pdf(self, x)
TypeError: in method 'BasicUniformDistribution_pdf', argument 2 of type 'double'
Do you have a suggested fix for the development team?
Please attach the input file(s) that generate this error. The simpler the input, the faster we can find the issue.

For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

  • 1. Is it tagged with a type: defect or task?
  • 2. Is it tagged with a priority: critical, normal or minor?
  • 3. If it will impact requirements or requirements tests, is it tagged with requirements?
  • 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users. it will cause crash, but not wrong results
  • 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

  • 1. If the issue is a defect, is the defect fixed?
  • 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
  • 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
  • 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
  • 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
@PaulTalbot-INL
Copy link
Collaborator

Approved for closure via #1008. No user-facing email is needed as this caused a crash, and is not of general interest.

wangcj05 pushed a commit that referenced this issue Aug 30, 2019
* new verbage

* Closes #1007

* andrea

* Closes #1003. Closes #973

* fixed ascii character problem

* cleaned csv loader

* skiped ui

* modified plugin test

* initial porting to PySide2

* oka

* removed folder accidentally added

* Scene needs to have the path item added.

* Switching to Qt5 because that is the default with Pyside2.

* Fixing problems with UI and python 3 compatibility.

* Qt5 does not have a rotate for simple text.

* Updating for python 3 and qt5/Pyside2

* Use Agg backend in windows, and nothing uses self.ddata so don't save

Even the docstring said it wasn't returned.

* addressed Paul comment

* reverted input param for global grid
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants