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.


Messages - rsam1993

Pages: [1] 2
1
Uncertainty Quantification (quoFEM) / Re: Parallel execution on a Windows HPC
« on: November 12, 2023, 01:26:18 AM »
Hi,

Thanks for teh update. I believe I should be still able to use the interface and call all the 128 cores, so the sampling and opensees analyses will be done and then using those results, I should be able to calculate the mean, standard deviation and other outputs separately.

But, hopefully, this issue can be fixed at some point.

2
Uncertainty Quantification (quoFEM) / Re: Parallel execution on a Windows HPC
« on: November 01, 2023, 02:32:35 AM »
I have bad news,

I ran Dakota through the command prompt as you taught me before with 128 samples. During the analysis, the CPU is 100% occupied but I get an empty dakotaTab.out at the end, and the same error in the terminal (please see the attached screenshot). But there is no dakota.err file in the directory.

3
Uncertainty Quantification (quoFEM) / Re: Parallel execution on a Windows HPC
« on: October 31, 2023, 11:34:58 PM »
Honestly I do not remember if the dakotaTab.out was properly created when we did everything manually. Let me try it again and keep you posted.

4
Uncertainty Quantification (quoFEM) / Re: Parallel execution on a Windows HPC
« on: October 31, 2023, 01:40:34 AM »
Thank you for your prompt response,

Yes, dakotaTab.out is created, but the results are not there. It seems to me that the dakota.out file is not completely generated by QuoFEM. I am attaching all the files you mentioned so you can check them all and see where this issue comes from.



5
Uncertainty Quantification (quoFEM) / Re: Parallel execution on a Windows HPC
« on: October 29, 2023, 08:04:05 PM »
Dear Sang-ri,

I have updated the QuoFEm application on our HPC and located the config.jason file in the same directory as the QuoFEM executable. Now when I run it with 128 samples all the 128 cores are called and it seems the Opensees analyses are performing successfully, but I get this error at the end and QuoFEm does not give me any results!

Error Running Dakota: Too many processes (128) in wait_setupCurrent limit on processes = 64

And here is the error message that I get from dakota.err file:

Too many processes (128) in wait_setup
Current limit on processes = 64



I am not sure where the problem is, because it should work. Please let me know what you need me to share with you to find the reason for this error.

6
Uncertainty Quantification (quoFEM) / Re: Parallel execution on a Windows HPC
« on: October 29, 2023, 03:30:43 PM »
Sang-ri,

I really appreciate it. I will start using this new update soon and let you know in case there is any problem, which I doubt.

7
Uncertainty Quantification (quoFEM) / Re: Parallel execution on a Windows HPC
« on: August 31, 2023, 04:36:59 PM »
Dear Sang-ri

Hope all is well.

I was wondering if the issue we talked about in this topic has been resolved in QuoFEM yet. If not, do you know when the new update is going to be released?


Thanks,

8
Uncertainty Quantification (quoFEM) / Re: Run QuoFEM with OpenSeesSP
« on: August 20, 2023, 03:27:51 AM »
Thanks, Frank,

it worked with no issue. So as long as I want to use only one core since I do not need to use the mpi command this method does the trick.

Thank you so much,

9
Uncertainty Quantification (quoFEM) / Run QuoFEM with OpenSeesSP
« on: August 17, 2023, 10:15:40 PM »
Dear all,

I am working on a large bridge model in OpenSees, and to conduct time-history analysis I use OpenSeesSP but with only one core (I cannot use more than one core due to some issues in OpenSees source which has not been addressed). However, since in OpenSeesSP, I can switch to the Mumps system the analysis is much faster than those performed with regular OpenSees.

Now I would like to know if there is any way to substitute the regular OpenSees in the QuoFEM directory with OpenSeesSP and do the forward propagation analysis with the QuoFEM user interface. I know the OpenSees executable file in the QuoFEM directory can be easily replaced by OpenSeesSP executable, but I do not know how can I change the commands to call OpenSeesSP and define the MPI executable and number of processors. (i.e. OpenSeesSP needs to be executed with the following command line: mpiexec -np numProcs? OpenSeesSP model.tcl )

I would be thankful if you can provide me with some details about how to apply this procedure if it is feasible.


Best regards,

10
Uncertainty Quantification (quoFEM) / Re: Parallel execution on a Windows HPC
« on: July 11, 2023, 02:00:29 AM »
Very good.

Thank you for your help and support.

11
Uncertainty Quantification (quoFEM) / Re: Parallel execution on a Windows HPC
« on: July 10, 2023, 06:29:31 PM »
Good news!

It is finally working and with this method, all the 128 cores of the CPU are occupied and the CPU utilization is 100% now. So, how can we fix the QuoFEM itself to do this automatically? Should I wait for a new update from your side?

12
Uncertainty Quantification (quoFEM) / Re: Parallel execution on a Windows HPC
« on: July 08, 2023, 04:21:50 PM »
I applied that change and still getting this error. Seems python cannot be called or found.


C:\Users\rsamtaslimi\Documents\quoFEM\LocalWorkDir\tmp.SimCenter\workdir.128>C:/quoFEM_Windows_Download/applications/python writeParam.py paramsDakota.in params.in
'C:/quoFEM_Windows_Download/applications/python' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\rsamtaslimi\Documents\quoFEM\LocalWorkDir\tmp.SimCenter\workdir.128>call ./driver.bat

C:\Users\rsamtaslimi\Documents\quoFEM\LocalWorkDir\tmp.SimCenter\workdir.128>"C:/quoFEM_Windows_Download/applications/performUQ/templateSub/simCenterSub.exe" params.in SimCenterInput.RV SimCenterInput.tcl

C:\Users\rsamtaslimi\Documents\quoFEM\LocalWorkDir\tmp.SimCenter>ERROR: simCenterDprepro could not open: params.in

C:\Users\rsamtaslimi\Documents\quoFEM\LocalWorkDir\tmp.SimCenter\workdir.128>C:/quoFEM_Windows_Download\applications\opensees\bin\OpenSees SimCenterInput.tcl  1>ops.out 2>&1

13
Uncertainty Quantification (quoFEM) / Re: Parallel execution on a Windows HPC
« on: July 07, 2023, 09:49:40 PM »
Hi Sang-ri,

I did the second approach but I am still getting the same error, which means I am doing something wrong.

Here is the modified "workflow_driver1.bat" and "driver.bat" after I replaced the commands "python" and "opensees" to {python path} and {opensees path}. Let me know if there is anything wrong here, please.

workflow_driver1.bat:

C:/quoFEM_Windows_Download/applications/python writeParam.py paramsDakota.in params.in
call ./driver.bat



driver.bat:

"C:/quoFEM_Windows_Download/applications/performUQ/templateSub/simCenterSub.exe" params.in SimCenterInput.RV SimCenterInput.tcl
C:/quoFEM_Windows_Download\applications\opensees\bin SimCenterInput.tcl 1> ops.out 2>&1

14
Uncertainty Quantification (quoFEM) / Re: Parallel execution on a Windows HPC
« on: July 07, 2023, 02:57:39 PM »
The procedure you described seems straightforward and I believe I did it right, but it does not work correctly. It only makes 128 workdir folders while I expect 150 (the analysis was done using 150 samples) and there are other errors regarding some required files which cannot be found when I run dakota.in through the command prompt.  Here is some part of the errors I got:


C:\Users\rsamtaslimi\Documents\quoFEM\LocalWorkDir\tmp.SimCenter\workdir.127>python writeParam.py paramsDakota.in params.in
'python' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\rsamtaslimi\Documents\quoFEM\LocalWorkDir\tmp.SimCenter\workdir.127>call ./driver.bat

C:\Users\rsamtaslimi\Documents\quoFEM\LocalWorkDir\tmp.SimCenter\workdir.127>"C:/quoFEM_Windows_Download/applications/performUQ/templateSub/simCenterSub.exe" params.in SimCenterInput.RV SimCenterInput.tcl
ERROR: simCenterDprepro could not open: params.in

C:\Users\rsamtaslimi\Documents\quoFEM\LocalWorkDir\tmp.SimCenter\workdir.127>OpenSees SimCenterInput.tcl  1>ops.out 2>&1
nonblocking fork: workflow_driver1.bat paramsDakota.in results.out
Second pass: scheduling 22 remaining local asynchronous jobs
Waiting on completed jobs
Too many processes (128) in wait_setup
Current limit on processes = 64

C:\Users\rsamtaslimi\Documents\quoFEM\LocalWorkDir\tmp.SimCenter\workdir.128>python writeParam.py paramsDakota.in params.in
'python' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\rsamtaslimi\Documents\quoFEM\LocalWorkDir\tmp.SimCenter\workdir.128>call ./driver.bat

C:\Users\rsamtaslimi\Documents\quoFEM\LocalWorkDir\tmp.SimCenter\workdir.128>"C:/quoFEM_Windows_Download/applications/performUQ/templateSub/simCenterSub.exe" params.in SimCenterInput.RV SimCenterInput.tcl

C:\Users\rsamtaslimi\Documents\quoFEM\LocalWorkDir\tmp.SimCenter>ERROR: simCenterDprepro could not open: params.in

C:\Users\rsamtaslimi\Documents\quoFEM\LocalWorkDir\tmp.SimCenter\workdir.128>OpenSees SimCenterInput.tcl  1>ops.out 2>&1

15
Uncertainty Quantification (quoFEM) / Re: Parallel execution on a Windows HPC
« on: July 06, 2023, 03:18:08 PM »
Here is the info written in dakota.in file. It is interesting because the number is 64! Then why the CPU utilization is still around 60%?

interface
  analysis_driver = 'workflow_driver1.bat'
  fork
   parameters_file = 'paramsDakota.in'
   results_file = 'results.out'
   aprepro
   work_directory
     named 'workdir'
     directory_tag
     directory_save
     file_save
     copy_files = 'templatedir/*'
  asynchronous evaluation_concurrency = 64


Pages: [1] 2