Recent Posts

Pages: [1] 2 3 ... 10
Thank very much you for the helpful suggestions, I will let you know
Regional Hazard Simulation (R2D, rWhale) / Re: Result Displaying Request
« Last post by fmk on June 11, 2022, 06:49:58 AM »
you need to open up Preferences and point the path to the Python interpreter. The interpreter is required to have the NHERI-simCenter module pip installed.
You can also try increasing the standard deviation to have a wider prior, as 10% coefficient of variation results in a narrow, informative prior. If the predictions from the model evaluated at the samples drawn from the prior are all too far away from the data, this can cause numerical difficulties during the algorithm run.

Using a log-normal prior instead of a normal prior will ensure that the input parameter values are admissible, if the parameters should always have positive values.
The most common reason for this to happen is that the number of requested samples is small in comparison to the number of parameters to be estimated. This can make the sample covariance matrix ill-conditioned, which causes difficulties when generating new sample points. As a result, during subsequent stages of the TMCMC algorithm, new sample points might not be accepted and each workdir will end up with the same parameter value.

However, since increasing the sample size to a larger number did not resolve the problem, I am not sure what could be the cause of the issue.. It would help if I can reproduce the issue, to diagnose the source of the problem. Sharing the model script or the contents of one of the workdirs will let me recreate the analysis on my machine and help identify the cause.
Aakash, what are the circumstances for which the is going to be the same in each workdir.
1. We are updating the doc on this type of usage, here is a heads up if you want to try in out .. you can get back to me if you have issues (it will help me with the documentation, the other helper is an undergraduate student here at Berkeley). But the simplest way to get what you need is to run quoFEM locally once. In your Documents folder you will find a directory quoFEM and in that directory a file called debug.log. That file contains a line starting with PYTHON COMMAND: (mine looks like the following)

a. you need to create a folder in which quoFEM will run the input
b. in that folder, create a folder named templatedir
c. in templatedir, place all files that will be needed (including the input file for workflow .. we call it scInput.json if you are using the current quoFEM application)
d. from the terminal you need to issue a few commands (those commands will depend on where the application is installed and what your operating system is). I have modified the quoFEM application to when they run locally spit out these commands to the debug.log file (The debug.log file is located in your ~/Documents/quoFEM directory after you start the application and run a local run). Writing this I think I should also modify the application to pop up these commands in a dialog.

  The debug.log file contains in it a line with the words "PYTHON COMMAD" which you can search for. The following was in my debug.log file.

PYTHON COMMAND "source $HOME/.bash_profile; export PATH=/Library/Frameworks/Python.framework/Versions/3.8/bin:/Users/fmckenna/release/WE-UQ/build/$PATH; \"/Library/Frameworks/Python.framework/Versions/3.8/bin/python3\" \"/Users/fmckenna/release/SimCenterBackendApplications/applications/Workflow/\" runningLocal \"/Users/fmckenna/Documents/WE-UQ/LocalWorkDir/tmp.SimCenter/templatedir/scInput.json\" \"/Users/fmckenna/release/SimCenterBackendApplications/applications/Workflow/WorkflowApplications.json\"" ()

    From this line you can create a .bat file or a .sh file (depending on your operating system) .. that file splits up the command above into a number of line & removes the \" .. for example, I would create a file from the above with the following:

source $HOME/.bash_profile;
export PATH=/Library/Frameworks/Python.framework/Versions/3.8/bin:/Users/fmckenna/release/quoFEM/build/$PATH;
/Library/Frameworks/Python.framework/Versions/3.8/bin/python3 /Users/fmckenna/release/quoFEM/build/
 runningLocal /Users/fmckenna/Documents/quoFEM/LocalWorkDir/tmp.SimCenter/templatedir/scInput.json /Users/fmckenna/release/quoFEM/build/

    This file I copy now to templatedir and run.

2.A second approach underway is creation of a jupyter notebook created that is an example of using the quoFEM backend that is being finished. It will be done by end September.
Regional Hazard Simulation (R2D, rWhale) / Re: Result Displaying Request
« Last post by will2019 on June 04, 2022, 09:07:14 PM »
Hello, thank you very much for your feedback. In fact i had run it remotely, but as you suggested, i run it locally but got this message : *Could not find Python on the system* even if python is well install on my sytem. Thanks
I wonder whether any recent development happened or not about this request.

All the best.

I am afraid I should send the whole ambient. The matter is that I don't read any warning or error and the output files are produced but the params files ( the procedure produces in each of the directories (workdir.#) are exactly the same. The problem generates before the model script is executed. It sems to me the procedure dedicated to produce random values input  params file (different for each workdir) does not work properly in this case, I don't know, pheraps due to an ambient configuration variable, although I have tryed to set everything at my best (not sufficient).
Can you please share your model script, in a private message if you would prefer, so that I can reproduce the issue and try a few solutions?
Pages: [1] 2 3 ... 10