31
Uncertainty Quantification (quoFEM) / Re: Error Running Dakota: Expected 0 gradients but found 1.
« on: December 07, 2022, 05:27:59 PM »
Glad to know it worked. Thanks for letting us know! 
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
32
Uncertainty Quantification (quoFEM) / Re: Error Running Dakota: Expected 0 gradients but found 1.
« on: December 05, 2022, 08:02:54 PM »
Hello, thanks for posting the issue!
Perhaps the model output file (results.out) is not written in the correct format. To check this, please inspect the "results.out" file under the cache folder "LocalWorkDir\tmp.SimCenter\workdir.1". The file should contain only the numbers and spaces (or tabs) and not the brackets. Dakota uses brackets to indicate the gradient values of the model - so having additional brackets there could have prompted the error.
If this is the case, please modify your main or postprocessing FEM scripts such that it only writes the numbers. If this is not the case, can you please share the below two files with us to help us identify the cause of the error?
(1)LocalWorkDir\tmp.SimCenter\workdir.1\results.out
(2)LocalWorkDir\tmp.SimCenter\dakota.in
Thanks,
Sang-ri
Perhaps the model output file (results.out) is not written in the correct format. To check this, please inspect the "results.out" file under the cache folder "LocalWorkDir\tmp.SimCenter\workdir.1". The file should contain only the numbers and spaces (or tabs) and not the brackets. Dakota uses brackets to indicate the gradient values of the model - so having additional brackets there could have prompted the error.
If this is the case, please modify your main or postprocessing FEM scripts such that it only writes the numbers. If this is not the case, can you please share the below two files with us to help us identify the cause of the error?
(1)LocalWorkDir\tmp.SimCenter\workdir.1\results.out
(2)LocalWorkDir\tmp.SimCenter\dakota.in
Thanks,
Sang-ri
33
Uncertainty Quantification (quoFEM) / Re: Local Failure Setting up Dakota
« on: November 17, 2022, 12:17:33 AM »
Hello Charles,
Thanks for posting the issue.
We currently do not support designsafe run for the "Import data files" option of GSA. Because it does not involve the model simulations (i.e. computationally intensive part), we thought users would not benefit much from running remotely.
However, it could be added. Please let us know if you deem it useful.
Sang-ri
Thanks for posting the issue.
We currently do not support designsafe run for the "Import data files" option of GSA. Because it does not involve the model simulations (i.e. computationally intensive part), we thought users would not benefit much from running remotely.
However, it could be added. Please let us know if you deem it useful.
Sang-ri
34
Uncertainty Quantification (quoFEM) / Re: Error running Forward Propogation example with OpenSeesPY
« on: November 10, 2022, 07:33:11 PM »
Great to know it worked! Thanks for sharing the log.
35
Uncertainty Quantification (quoFEM) / Re: Error running Forward Propogation example with OpenSeesPY
« on: November 10, 2022, 06:36:36 PM »
Hello Ahmet,
Thank you for posting the issue and sharing the input files.
The issue might be because the python executable that quoFEM uses does not have the package "opsvis" installed. To confirm this, please check the error message written in C:/Users/DELL/Documents/quoFEM/LocalWorkDir/tmp.SimCenter/workdir.1/ops.out.
If this is the case, you can either modify the code not to use the package (if possible
) or install the additional packages to the python executable that quoFEM uses. To see how to install additional python packages, please go to Section 3.2.2 Python in the documentation and find the yellow text box that says "Python on Windows".
Please let us know if it works!
Thank you for posting the issue and sharing the input files.
The issue might be because the python executable that quoFEM uses does not have the package "opsvis" installed. To confirm this, please check the error message written in C:/Users/DELL/Documents/quoFEM/LocalWorkDir/tmp.SimCenter/workdir.1/ops.out.
If this is the case, you can either modify the code not to use the package (if possible
) or install the additional packages to the python executable that quoFEM uses. To see how to install additional python packages, please go to Section 3.2.2 Python in the documentation and find the yellow text box that says "Python on Windows".Please let us know if it works!
36
Uncertainty Quantification (quoFEM) / Re: using uq module as a standalone tool
« on: October 12, 2022, 10:42:48 PM »
Hi Anne,
Thanks for the clarification. If you simply need to generate samples from a truncated lognormal distribution, I would not recommend you use quoFEM (Although we can do it by generating standard uniform samples and providing a model that transforms the samples to truncated lognormal space)
Instead, to my understanding, the 'rejection sampling' described below seem to be the quickest way of getting samples from truncated lognormal:
1. Generate a larger set of samples from the original lognormal distribution, for example, using stats.lognorm.rvs()
2. Discard all the samples below the truncation threshold and use only the ones within the valid range.
Please let me know if I am missing something or if you wanted to get the PDF or CDF of the truncated lognormal distribution instead of its samples.
Thanks,
Sang-ri
Thanks for the clarification. If you simply need to generate samples from a truncated lognormal distribution, I would not recommend you use quoFEM (Although we can do it by generating standard uniform samples and providing a model that transforms the samples to truncated lognormal space)
Instead, to my understanding, the 'rejection sampling' described below seem to be the quickest way of getting samples from truncated lognormal:
1. Generate a larger set of samples from the original lognormal distribution, for example, using stats.lognorm.rvs()
2. Discard all the samples below the truncation threshold and use only the ones within the valid range.
Please let me know if I am missing something or if you wanted to get the PDF or CDF of the truncated lognormal distribution instead of its samples.
Thanks,
Sang-ri
37
Uncertainty Quantification (quoFEM) / Re: using uq module as a standalone tool
« on: October 12, 2022, 05:31:49 PM »
Hi Anne,
Thanks for asking this! Can you help us better understand the task by giving more details or maybe pointing us to a reference that shows your objective?
For example, we are wondering:
1. Do you need to 'calibrate' the truncated lognormal or do you want to 'sample' from it using quoFEM (or is it both)? If it is the former, it would be helpful if we knew the type of dataset used to calibrate the fragility curve. If it is the latter, we can provide a new distribution in the RV panel.
2. Do you consider this only in quoFEM, or are you envisioning using the truncated lognormal distribution on EEUQ and other tools as well?
Sang-ri
Thanks for asking this! Can you help us better understand the task by giving more details or maybe pointing us to a reference that shows your objective?
For example, we are wondering:
1. Do you need to 'calibrate' the truncated lognormal or do you want to 'sample' from it using quoFEM (or is it both)? If it is the former, it would be helpful if we knew the type of dataset used to calibrate the fragility curve. If it is the latter, we can provide a new distribution in the RV panel.
2. Do you consider this only in quoFEM, or are you envisioning using the truncated lognormal distribution on EEUQ and other tools as well?
Sang-ri
38
General Questions / Re: Monte Carlo (OpenSeespy)
« on: October 07, 2022, 06:52:38 PM »
I am sorry you are still getting errors. If you would like a quick Zoom meeting to solve this issue, please send me your available times by private message or email.
Otherwise, it would be helpful if you could take a screenshot of the templatedir directory (that contains the list of files created) in the local working directory.
Some of the reasons we get the python exit code 1 error are:
1. When a file inside the Local working directory is opened or used by another program
2. When the python nheri_simcenter package is not properly installed
3. Onedrive sync (when it is online-only mode) had caused issues previously, so that could be one possibility
Otherwise, it would be helpful if you could take a screenshot of the templatedir directory (that contains the list of files created) in the local working directory.
Some of the reasons we get the python exit code 1 error are:
1. When a file inside the Local working directory is opened or used by another program
2. When the python nheri_simcenter package is not properly installed
3. Onedrive sync (when it is online-only mode) had caused issues previously, so that could be one possibility
39
General Questions / Re: Monte Carlo (OpenSeespy)
« on: October 07, 2022, 05:25:34 PM »
This is indeed an interesting issue, and your feedback here is very helpful for us. We greatly appreciate it.
1. "File cannot be accessed" error
I think the python.exe in the WindowsApps folder is not a python executable (what we wanted), but a python installer. You can just ignore it or get rid of it by turning off the 'App installer (python.exe)' button in the Manage app execution aliases.
If you got only this path from the command prompt, that means you do not have a system default python executable, which is perfectly fine.
2. Finding the python.exe path that jupyter notebook (or spyder) uses
So instead of the system python path, we want to grab the path to python.exe that is used in the jupyter notebook - such that we know it works with your model (I presume you used jupyter notebook to develop and test the model). To get this path, you can use the following command in the jupyter notebook
import sys
sys.executable
which will show you the python exe that is currently running. Then please change the quoFEM python path to what is shows.
3. The version that worked for me
I had python 3.9.8 installed on my windows laptop which I downloaded from the python website, and I updated the openseespy package to the latest version for this testing.
Sang-ri
1. "File cannot be accessed" error
I think the python.exe in the WindowsApps folder is not a python executable (what we wanted), but a python installer. You can just ignore it or get rid of it by turning off the 'App installer (python.exe)' button in the Manage app execution aliases.
If you got only this path from the command prompt, that means you do not have a system default python executable, which is perfectly fine.
2. Finding the python.exe path that jupyter notebook (or spyder) uses
So instead of the system python path, we want to grab the path to python.exe that is used in the jupyter notebook - such that we know it works with your model (I presume you used jupyter notebook to develop and test the model). To get this path, you can use the following command in the jupyter notebook
import sys
sys.executable
which will show you the python exe that is currently running. Then please change the quoFEM python path to what is shows.
3. The version that worked for me
I had python 3.9.8 installed on my windows laptop which I downloaded from the python website, and I updated the openseespy package to the latest version for this testing.
Sang-ri
40
General Questions / Re: Monte Carlo (OpenSeespy)
« on: October 06, 2022, 03:56:51 PM »
Hi
Thanks much for sharing the input files. It was very helpful. The following was needed for me to make it run on quoFEM
1. Uncomment the last three lines
Those look like the correct way of writing results.out for the maximum load.
2. Change the python path to your own system python path
Currently, the Windows version of quoFEM is distributed with its own python exe (v3.8) and OpenSeesPy (v3.3.0.1). But I think some of your functions only work with OpenSeesPy v3.4, which requires python v3.9. To solve this issue, you can make quoFEM use your system python exe instead the default one. To do this, go to file-preferences and check 'custom python' and change the path to the system python path (You can find the system python path by typing 'where.exe python' on the command prompt). Also, to make sure all the SimCenter dependencies are installed in this python exe, do 'pip install nheri_simcenter --upgrade'
3. Comment out IPython and matplotlib
I commented out the lines related to IPython and plt.show(). When I tested the input script (by typing 'python Benchmarked_Rectangular_Encased_column_quoFEM.py'), these parts were blocking the analysis.
4. Created params.py file
I picked up the following lines from the main script and moved them to params.py
Please do #2 and then try running the analysis with the attached scripts (to have #1,#2, and #4) and let us know how it goes!
Sang-ri
Thanks much for sharing the input files. It was very helpful. The following was needed for me to make it run on quoFEM
1. Uncomment the last three lines
Those look like the correct way of writing results.out for the maximum load.
2. Change the python path to your own system python path
Currently, the Windows version of quoFEM is distributed with its own python exe (v3.8) and OpenSeesPy (v3.3.0.1). But I think some of your functions only work with OpenSeesPy v3.4, which requires python v3.9. To solve this issue, you can make quoFEM use your system python exe instead the default one. To do this, go to file-preferences and check 'custom python' and change the path to the system python path (You can find the system python path by typing 'where.exe python' on the command prompt). Also, to make sure all the SimCenter dependencies are installed in this python exe, do 'pip install nheri_simcenter --upgrade'
3. Comment out IPython and matplotlib
I commented out the lines related to IPython and plt.show(). When I tested the input script (by typing 'python Benchmarked_Rectangular_Encased_column_quoFEM.py'), these parts were blocking the analysis.
4. Created params.py file
I picked up the following lines from the main script and moved them to params.py
- hp=280 #height of the profile
- bp=280 #width of the profile
- fy=426 #profile yield
- Ey=210000 #profile E modul
Please do #2 and then try running the analysis with the attached scripts (to have #1,#2, and #4) and let us know how it goes!
Sang-ri
41
General Questions / Re: Monte Carlo (OpenSeespy)
« on: October 05, 2022, 03:42:59 PM »
Can you check the below to help us identify the issue?
1. Is the 'results.out' (in workdir.23) empty?
2. Is 'ops.out' created in workdir.23? The error log from OpenSeespy should be written here. If ops.out is not there, can you try the following? (1) open Command Prompt (if Windows) or terminal (if Mac) (2) navigate to workdir.23 using 'cd' command (3) type driver.bat (windows) or ./driver (mac) (4) check if you get any errors and if results.out is properly written.
Please let me know if you have questions.
1. Is the 'results.out' (in workdir.23) empty?
2. Is 'ops.out' created in workdir.23? The error log from OpenSeespy should be written here. If ops.out is not there, can you try the following? (1) open Command Prompt (if Windows) or terminal (if Mac) (2) navigate to workdir.23 using 'cd' command (3) type driver.bat (windows) or ./driver (mac) (4) check if you get any errors and if results.out is properly written.
Please let me know if you have questions.
42
General Questions / Re: Monte Carlo (OpenSeespy)
« on: October 04, 2022, 04:07:06 PM »
Hello! Can you check if ops.out file is created in workdir.23 and share the contents with us?
43
Uncertainty Quantification (quoFEM) / Re: Error running Forward Propogation example with OpenSeesPY
« on: October 04, 2022, 05:46:34 AM »
Great! Currently, only Mac requires this additional pip install step.
Yes, if I understood the question correctly, clicking the right mouse button on the spreadsheet will change the variable of the x-axis in the plot.
Yes, if I understood the question correctly, clicking the right mouse button on the spreadsheet will change the variable of the x-axis in the plot.
44
Uncertainty Quantification (quoFEM) / Re: Error running Forward Propogation example with OpenSeesPY
« on: October 04, 2022, 05:06:07 AM »
Is openseespy installed on the laptop? If not, please run 'pip3 install nheri_simcenter --upgrade' to make sure all the dependencies (including openseespy) are installed.
Otherwise, can you please check if ops.out is created in the workdir.1 and share the contents with us?
Thank you,
Otherwise, can you please check if ops.out is created in the workdir.1 and share the contents with us?
Thank you,
45
Uncertainty Quantification (quoFEM) / Re: Running python analysis
« on: October 04, 2022, 05:01:15 AM »
We have actually changed the name from Openseespy to Python for the coming release (v3.2). It will be available within a few days. Thank you for the feedback