Chapter 1 examples 3 and 4 on Windows don't match manual

[rudyverderber]

I am running v 18.2.0 on windows(Cygwin).

Example 4 strain plot does not match the manual.

If I compare the end of output with the output provided, then some of the data matches (reactions, syy) while other data is quite different (sxx, szz,...).
Windows v 18.2.0 (4 threads)
structure vessel page no. 1

    step no.      52                        loading press_te
    stresses                      
  elem  cent         sigma_xx            sigma_yy            sigma_zz
                     sigma_xy            sigma_yz            sigma_xz
                     eng_dens            mises               c1      
                     c2                  c3      

   4482      1      506.594039          -17.741709          286.431419
                     -2.553535           -0.022078            1.921170
                      0.715885          456.062444            0.000191
                    456.351623            1.000000

   4474      1      480.513163          -14.610743          283.216122
                     -9.351400           -0.081717            1.721647
                      0.572980          432.041989            0.000000
                    456.375580            3.000000

   4386      1      442.158376          -14.902190          271.616722
                     -9.310997           -0.081349            1.488040
                      0.494760          400.386261            0.000000
                    456.410385            3.000000

   4378      1      407.080909          -14.749421          261.135993
                     -7.569651           -0.066097            1.273996
                      0.427794          371.288015            0.000000
                    456.445213            3.000000

   4356      1      392.513550          -14.742283          256.767078
                     -6.472893           -0.056543            1.184288
                      0.401544          359.349361            0.000000
                    456.462631            3.000000

    output reactions totals only 'react nodes'
  elem  cent         sigma_xx            sigma_yy            sigma_zz
                     sigma_xy            sigma_yz            sigma_xz
                     eng_dens            mises               c1      
                     c2                  c3      

  4482       1      -39.714525          -15.523197          427.182573
                     -2.784839           -0.016338           -4.090779
                      0.532257          455.366465            0.000106
                    456.347299            1.000000

  4474       1      -54.500370          -14.905684          419.867807
                     -1.687214           -0.005847           -4.155487
                      0.536134          455.930570            0.000123
                    456.383119            1.000000

  4386       1      -61.520359          -15.062703          416.017625
                     -0.641290            0.004245           -4.181395
                      0.539251          456.148139            0.000134
                    456.418586            1.000000

  4378       1      -64.532751          -15.126680          414.374298
                     -0.145754            0.009050           -4.192618
                      0.541439          456.274807            0.000140
                    456.453797            1.000000

  4356       1      -65.199477          -15.145125          414.025162
                      0.011333            0.010312           -4.192903
                      0.542307          456.321216            0.000142
                    456.471345            1.000000


output reactions totals only 'react nodes'

 Totals:        -0.67329E+07        -0.19639E+07        -0.17632E+06


 Totals:     -0.67329387E+07     -0.19638856E+07     -0.17632312E+06

provided output_temp_dependent
Mac OS X 17.5.4

  elem  cent         sigma_xx            sigma_yy            sigma_zz
                     sigma_xy            sigma_yz            sigma_xz
                     eng_dens            mises               c1      
                     c2                  c3      

  4482       1      -39.714525          -15.523197          427.182573
                     -2.784839           -0.016338           -4.090779
                      0.532257          455.366465            0.000106
                    456.347299            1.000000

  4474       1      -54.500370          -14.905684          419.867807
                     -1.687214           -0.005847           -4.155487
                      0.536134          455.930570            0.000123
                    456.383119            1.000000

  4386       1      -61.520359          -15.062703          416.017625
                     -0.641290            0.004245           -4.181395
                      0.539251          456.148139            0.000134
                    456.418586            1.000000

  4378       1      -64.532751          -15.126680          414.374298
                     -0.145754            0.009050           -4.192618
                      0.541439          456.274807            0.000140
                    456.453797            1.000000

  4356       1      -65.199477          -15.145125          414.025162
                      0.011333            0.010312           -4.192903
                      0.542307          456.321216            0.000142
                    456.471345            1.000000


output reactions totals only 'react nodes'

 Totals:        -0.67329E+07        -0.19639E+07        -0.17632E+06

For example 3, I get the general cylinder stresses, 1 of 6 T stresses, and the reaction nodes. I cannot get the K quantities and 5 of 6 T stresses. What am I doing wrong?

Thank you! Rudy  

[rhdodds]

Hi Rudy,

Thanks for the info.

I'll start looking at this ...

Would you please run the verification suites on your setup ?

Please get newest version from www.warp3d.net. This version uses Python 3 to drive execution of the verification suites in .../verification/run....py This change was made because most users never install Cygwin (so they have no Bash shell). I installed Python 3 into Cygwin a few weeks ago. The run..py codes execute ok.

Thanks,

Bob

[rudyverderber]

Hi Bob, I ran the run_tests and run_J_tests verification suites on 18.2.0 on Cygwin. The check values are correct to 6 or 7 places. ( I thought one test didn’t run due to MPI, but I couldn’t find it.) I downloaded version 18.2.1. 1. It is not quite clear to me if “Windows” is DOS style or Cygwin. I guess I got Cygwin to work, so I kept with it. Do you recommend DOS style or Cygwin? 1. Run_windows/warp3d.exe simply returns in 18.2.1 on DOS, while it works on 18.2.0. 2. The verifications scripts didn’t work the first time. I’ll let you know the results tomorrow. Thanks Rudy Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 From: Robert H Dodds Jr<mailto:notifications@github.com> Sent: Saturday, July 25, 2020 3:23 PM To: rhdodds/warp3d<mailto:warp3d@noreply.github.com> Cc: rudyverderber<mailto:rudyverderber@outlook.com>; Author<mailto:author@noreply.github.com> Subject: Re: [rhdodds/warp3d] Chapter 1 examples 3 and 4 on Windows don't match manual (#7) Hi Rudy, Thanks for the info. I'll start looking at this ... Would you please run the verification suites on your setup ? Please get newest version from www.warp3d.net<http://www.warp3d.net>. This version uses Python 3 to drive execution of the verification suites in .../verification/run....py This change was made because most users never install Cygwin (so they have no Bash shell). I installed Python 3 into Cygwin a few weeks ago. The run..py codes execute ok. Thanks, Bob — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#7 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/API4SVDCCCE7MPU4WGS4NA3R5MWLXANCNFSM4PHSBNGQ>.

[rhdodds]

Rudy,

======
On Jul 25, 2020, at 8:12 PM, rudyverderber notifications@github.com wrote:

Hi Bob,

I ran the run_tests and run_J_tests verification suites on 18.2.0 on Cygwin. The check values are correct to 6 or 7 places. ( I thought one test didn’t run due to MPI, but I couldn’t find it.)

I downloaded version 18.2.1.

1. It is not quite clear to me if “Windows” is DOS style or Cygwin. I guess I got Cygwin to work, so I kept with it. Do you recommend DOS style or Cygwin?

2. Run_windows/warp3d.exe simply returns in 18.2.1 on DOS, while it works on 18.2.0.

=> There is one Windows .exe as you have seen. Can be run under DOS or Cygwin environment. I use mostly Cygwin
since development work is done on Linux and macOS.

Prior to this release, the verification problems required Cygwin + Bash + Perl to run. Many Windows
users did not want to install Cygwin.

I rewrote the “driver” system to use only Python (3) last month. Windows users w/o Cygwin can
readily install Python 3 right from the Python web site. Run the verification suites in a
DOS command shell.

I installed Python3 from the Cygwin site and run the same run..py codes under the Bash shell.

=> Did you see the Quickstart Windows document ?

Bob

[rudyverderber]

Hi Bob, I’ll stick with Cygwin. Thanks. I reread the quickstart doc. I forgot to change the .dll name, and that got the executable to run. I also tried the OMP and MKL NUM_threads variables. I don’t think I need it without a cluster. Is that correct? I have run the run_tests and run_J_tests verification scripts using version 18.1.2. Like 18.2.0, the answers are as expected, except one problem didn’t match as shown below. I reran the chapter 1 example 4 problem in 18.2.1. Similar to 18.2.0, the output at the end in 18.2.1 is different from the output file included in the directory. Thanks, Rudy ... Check results: test72_out ... output file opened ... ... comparison value: 853 ... value from output file: 853 ... comparison value: 21 ... value from output file: 21 ... comparison value: 821 ... value from output file: 821 ... comparison value: 1 ... value from output file: list: **** difference in solution ... comparison value: 821 ... value from output file: list: **** difference in solution ... comparison value: 2053 ... value from output file: list: **** difference in solution ... comparison value: 51 ... value from output file: list: **** difference in solution ... comparison value: 1 ... value from output file: list: **** difference in solution ... done Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 From: Robert H Dodds Jr<mailto:notifications@github.com> Sent: Saturday, July 25, 2020 9:16 PM To: rhdodds/warp3d<mailto:warp3d@noreply.github.com> Cc: rudyverderber<mailto:rudyverderber@outlook.com>; Author<mailto:author@noreply.github.com> Subject: Re: [rhdodds/warp3d] Chapter 1 examples 3 and 4 on Windows don't match manual (#7) Rudy, ====== On Jul 25, 2020, at 8:12 PM, rudyverderber notifications@github.com<mailto:notifications@github.com> wrote: Hi Bob, I ran the run_tests and run_J_tests verification suites on 18.2.0 on Cygwin. The check values are correct to 6 or 7 places. ( I thought one test didn’t run due to MPI, but I couldn’t find it.) I downloaded version 18.2.1. 1. It is not quite clear to me if “Windows” is DOS style or Cygwin. I guess I got Cygwin to work, so I kept with it. Do you recommend DOS style or Cygwin? 2. Run_windows/warp3d.exe simply returns in 18.2.1 on DOS, while it works on 18.2.0. => There is one Windows .exe as you have seen. Can be run under DOS or Cygwin environment. I use mostly Cygwin since development work is done on Linux and macOS. Prior to this release, the verification problems required Cygwin + Bash + Perl to run. Many Windows users did not want to install Cygwin. I rewrote the “driver” system to use only Python (3) last month. Windows users w/o Cygwin can readily install Python 3 right from the Python web site. Run the verification suites in a DOS command shell. I installed Python3 from the Cygwin site and run the same run..py codes under the Bash shell. => Did you see the Quickstart Windows document ? Bob — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#7 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/API4SVGQPKXGNMELA3Q2UNTR5N7VJANCNFSM4PHSBNGQ>.

[rhdodds]

Hi Rudy,

A set of fixes in directory verification/test72 apparently got omitted.

Please get them from GitHub source this site or: https://www.dropbox.com/s/ule9thtpk6awepc/test72.zip?dl=0

Bob

[rudyverderber]

Hi Bob, I downloaded test72 link from the link. (It did not contain check_72.perl) The problem was not resolved. I checked the run output. It is correct. The problem is in check_72.perl. Following is the fix in 5 locations. Was: $partno = 7 ^ “list:” Should be: $partno = 8; ^ integer of interest Regards, Rudy Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 From: Robert H Dodds Jr<mailto:notifications@github.com> Sent: Sunday, July 26, 2020 9:11 AM To: rhdodds/warp3d<mailto:warp3d@noreply.github.com> Cc: rudyverderber<mailto:rudyverderber@outlook.com>; Author<mailto:author@noreply.github.com> Subject: Re: [rhdodds/warp3d] Chapter 1 examples 3 and 4 on Windows don't match manual (#7) Hi Rudy, A set of fixes in directory verification/test72 apparently got omitted. Please get them from GitHub source this site or: https://www.dropbox.com/s/ule9thtpk6awepc/test72.zip?dl=0 Bob — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#7 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/API4SVGJWOTB5S34HD4JLXTR5QTRXANCNFSM4PHSBNGQ>.

[rhdodds]

Hi Rudy,

1. By default, WARP3D runs Windows jobs in shared-memory parallel using
   the available number of threads on the processor.
   For a typical I7, this will be 4 "real" threads = 4 "physical cores" + 4 "hyperthreads".
   I normally run WARP3D jobs with the number of threads set = # physical cores -1 to
   leave one core for the (hundreds) of Windows OS processes.

2. Please check your WARP3D distribution. In the verification directory (and sub directories),
   the only .perl files should be in directories hybrid_*** for checking MPI runs on Linux.
   All other .perl files were removed at 18.2.1.

Working on the examples 3 and 4 in chpt 1 now.

Bob

[rudyverderber]

Hi Bob, (see below) Regards, Rudy Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 From: Robert H Dodds Jr<mailto:notifications@github.com> Sent: Sunday, July 26, 2020 1:33 PM To: rhdodds/warp3d<mailto:warp3d@noreply.github.com> Cc: rudyverderber<mailto:rudyverderber@outlook.com>; Author<mailto:author@noreply.github.com> Subject: Re: [rhdodds/warp3d] Chapter 1 examples 3 and 4 on Windows don't match manual (#7) Hi Rudy, 1. By default, WARP3D runs Windows jobs in shared-memory parallel using the available number of threads on the processor. For a typical I7, this will be 4 "real" threads = 4 "physical cores" + 4 "hyperthreads". I normally run WARP3D jobs with the number of threads set = # physical cores -1 to leave one core for the (hundreds) of Windows OS processes. (I have an I7-8700 6 cores and 12 logical cores. When I run I specify 4 (prior to redirected input) in the command line.) 1. Please check your WARP3D distribution. In the verification directory (and sub directories), the only .perl files should be in directories hybrid_*** for checking MPI runs on Linux. All other .perl files were removed at 18.2.1. (The scripts did not run on Cygwin. So I copied all missing files from 18.2.0 into 18.2.1. Ooops. I started over with a clean directory. Then per pptx I ran the regular and J verifications in Windows (DOS). The results are pretty close. K_2 was not accurate (1% error) as shown below. Would you expect this script to run in Cygwin? If yes, I copied my error messages.) Working on the examples 3 and 4 in chpt 1 now. (I am interested in mastering these approaches.) Bob ... Checking results: testK_2_out .... comparison value: 0.3565E+00 .... value from output: 0.3595E+00 **** difference in solution $ python3 run_tests.py Output from running python script on Cygwin….

>> Running with Python version: 3.6 >> Number of threads to use: 4

Traceback (most recent call last): File "run_tests.py", line 725, in <module> if __name__ == "__main__": main() File "run_tests.py", line 652, in main initialize() File "run_tests.py", line 512, in initialize 'set MKL_NUM_THREADS='+str_threads UnboundLocalError: local variable 'continuation' referenced before assignment — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#7 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/API4SVCK42L7OZU5QX6D7QDR5RSGDANCNFSM4PHSBNGQ>.

[rhdodds]

Hi Rudy,

1. testK_2 continues to be a challenge. The solutions vary about 1% between runs and across platforms. I have looked for the bug off and on for about a year. Shows up with by Intel fortran and gfortran. I've used Valgrind and memcheck w/o success in locating the problem.

2. I just ran (again) the run_tests.py and run_J_tests.py on W10, cygwin. Ran fine. The repository has the same versions I'm running. I note that your Cygwin Python is 3.6. My Cygwin Python is 3.8.3.
   Would you please (1) get the repository versions of the two run...py codes, (2) update your Cygwin Python to current version (3.8.3) ?

The issues you found for manual Chpt 1 example 3. I should provide 3 separate input files. (1) for internal
pressure loading, (2) for crack face pressure loading, (3) for just thermal loading. Then also 3 corresponding output files
for comparison. The computed results are fine and agree with those in the Tables in Chpt 1. Will get that straightened out and update example_3 files.

Bob

[rudyverderber]

Hi Bob, (see below) Rudy Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 From: Robert H Dodds Jr<mailto:notifications@github.com> Sent: Sunday, July 26, 2020 9:58 PM To: rhdodds/warp3d<mailto:warp3d@noreply.github.com> Cc: rudyverderber<mailto:rudyverderber@outlook.com>; Author<mailto:author@noreply.github.com> Subject: Re: [rhdodds/warp3d] Chapter 1 examples 3 and 4 on Windows don't match manual (#7) Hi Rudy, 1. testK_2 continues to be a challenge. The solutions vary about 1% between runs and across platforms. I have looked for the bug off and on for about a year. Shows up with by Intel fortran and gfortran. I've used Valgrind and memcheck w/o success in locating the problem. 2. I just ran (again) the run_tests.py and run_J_tests.py on W10, cygwin. Ran fine. The repository has the same versions I'm running. I note that your Cygwin Python is 3.6. My Cygwin Python is 3.8.3. Would you please (1) get the repository versions of the two run...py codes, (2) update your Cygwin Python to current version (3.8.3) ? (Using python3.8.3 (updated today) on my machine produces the same error messages. On my end, I am fine running the windows DOS command shell.) The issues you found for manual Chpt 1 example 3. I should provide 3 separate input files. (1) for internal pressure loading, (2) for crack face pressure loading, (3) for just thermal loading. Then also 3 corresponding output files for comparison. The computed results are fine and agree with those in the Tables in Chpt 1. Will get that straightened out and update example_3 files. (I gathered that the 3 loads had to be commented. For the crack face pressure, I suspected “ crack face tractions ty 15.2,” also needs to be uncommented. User changes to the input file may be a source of the problem. I am a paraview user. I assume the internal pressure (ch3 ex 3&4) is on the inside surfaces (minus the flaw) and the crack face pressure is on the inside of the flaw. I oddly suspect that the face doesn’t include the tip. I am somewhat tempted to write the bc surfaces and points to an exodus (vtk) file. For preprocessing, I noticed that quest provided a commercial product. Is there a recommended open source preprocessing package?) Bob $ python3.8 -V Python 3.8.3 $ python3.8 run_tests.py

>> Running with Python version: 3.8 >> Number of threads to use: 4

Traceback (most recent call last): File "run_tests.py", line 725, in <module> if __name__ == "__main__": main() File "run_tests.py", line 652, in main initialize() File "run_tests.py", line 511, in initialize threads = 'set OMP_NUM_THREADS='+str_threads + continuation + \ UnboundLocalError: local variable 'continuation' referenced before assignment — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#7 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/API4SVAJZI3TN45EMLHHXK3R5TNKNANCNFSM4PHSBNGQ>.

[rudyverderber]

In addition to comments below, I found the source of the script issue. Platform.system does not return programmed option. … os_name = platform.system() print (" os_name 1 ", os_name, "\n") windows = os_name == 'Windows' linux = os_name == 'Linux' osx = os_name == 'Darwin' print (" os_name 2 ", os_name, "\n") if "WARP3D_HOME" in os.environ: $ python3.8 run_tests.py

>> Running with Python version: 3.8

os_name 1 CYGWIN_NT-10.0-18363 os_name 2 CYGWIN_NT-10.0-18363

>> Number of threads to use:

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 From: Robert H Dodds Jr<mailto:notifications@github.com> Sent: Sunday, July 26, 2020 9:58 PM To: rhdodds/warp3d<mailto:warp3d@noreply.github.com> Cc: rudyverderber<mailto:rudyverderber@outlook.com>; Author<mailto:author@noreply.github.com> Subject: Re: [rhdodds/warp3d] Chapter 1 examples 3 and 4 on Windows don't match manual (#7) Hi Rudy, 1. testK_2 continues to be a challenge. The solutions vary about 1% between runs and across platforms. I have looked for the bug off and on for about a year. Shows up with by Intel fortran and gfortran. I've used Valgrind and memcheck w/o success in locating the problem. 2. I just ran (again) the run_tests.py and run_J_tests.py on W10, cygwin. Ran fine. The repository has the same versions I'm running. I note that your Cygwin Python is 3.6. My Cygwin Python is 3.8.3. Would you please (1) get the repository versions of the two run...py codes, (2) update your Cygwin Python to current version (3.8.3) ? The issues you found for manual Chpt 1 example 3. I should provide 3 separate input files. (1) for internal pressure loading, (2) for crack face pressure loading, (3) for just thermal loading. Then also 3 corresponding output files for comparison. The computed results are fine and agree with those in the Tables in Chpt 1. Will get that straightened out and update example_3 files. Bob — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#7 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/API4SVAJZI3TN45EMLHHXK3R5TNKNANCNFSM4PHSBNGQ>.

[rhdodds]

Hi Rudy,

1. The code run_tests.py in verification directory on GitHub does recognize Cygwin. That code has stms:

ver = sys.version_info
print("\n\n>>> Running with Python version: "
+ str(ver.major)+'.'+str(ver.minor))
if ver.major == 3 and ver.minor <= 4:
print('\n\n >>>>>>>>>>>>> Please upgrade to Python 3.5 or newer')
print(' Execution terminated\n\n')
exit(0)

os_name = platform.system()
windows = os_name == 'Windows'
linux = os_name == 'Linux'
osx = os_name == 'Darwin'
cygwin = False
if 'CYGWIN' in os_name: cygwin = True <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
....
....

if cygwin :
continuation = ';'
print(">>> Platform: Cygwin (Windows). Only Intel Fortran version supported\n" )
warp_name = '$WARP3D_HOME"/run_windows/warp3d.exe" '

2. Example 3 in Chpt 1. Crack face loading. You are correct. I don't believe the elements incident on the front have the traction applied. However, that omission will not impact the solution more that a tiny fraction of a percent given the vanishing small area of those elements.

3. Pre-processors. Post-processing of WARP3D results using the open-source ParaView code is our default go to solution and has been for 5+ years.

   For mesh generation, there does not exist (to my knowledge) an open-source code of the same extensive capabilities, runs on all 3 platforms,
   ....

We use Patran and many other users adopt FEMAP. Both are commercial and have very wide use. FEMAP outputs Patran neutral files which the patwarp program in our distribution processes. These codes build complete models: geometry, meshing, loadings and boundary conditions of all types. For specialized crack models, we use FEACrack which offers WARP3D as one solution option (we have no financial relationship with the FEACrack folks).

The open source code GMSH may provide some users with an adequate solution. We have a beta Python program which converts the Abaqus style *.inp file output by GMSH into a WARP3D input file. The code handles
tet4, tet10, hex8 and hex20 elements. We're developing some experience with GMSH but are not sure yet that it will impose many types of loading and boundary conditions. But at least the nodal coordinates, element types, and connectivities are translated. This may be sufficient for many users.

Bob

[rudyverderber]

Hi Bob, I downloaded the verification script files from GitHub. They run correctly on Cygwin (py3.6) as you indicated. I am mostly interested in matching the examples 3 and 4 in chapter 1. (What am I doing wrong?) Thanks Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 From: Robert H Dodds Jr<mailto:notifications@github.com> Sent: Monday, July 27, 2020 11:28 AM To: rhdodds/warp3d<mailto:warp3d@noreply.github.com> Cc: rudyverderber<mailto:rudyverderber@outlook.com>; Author<mailto:author@noreply.github.com> Subject: Re: [rhdodds/warp3d] Chapter 1 examples 3 and 4 on Windows don't match manual (#7) Hi Rudy, 1. The code run_tests.py in verification directory on GitHub does recognize Cygwin. That code has stms: ver = sys.version_info print("\n\n>>> Running with Python version: " + str(ver.major)+'.'+str(ver.minor)) if ver.major == 3 and ver.minor <= 4: print('\n\n >>>>>>>>>>>>> Please upgrade to Python 3.5 or newer') print(' Execution terminated\n\n') exit(0) os_name = platform.system() windows = os_name == 'Windows' linux = os_name == 'Linux' osx = os_name == 'Darwin' cygwin = False if 'CYGWIN' in os_name: cygwin = True <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< .... .... if cygwin : continuation = ';' print(">>> Platform: Cygwin (Windows). Only Intel Fortran version supported\n" ) warp_name = '$WARP3D_HOME"/run_windows/warp3d.exe" ' 1. Example 3 in Chpt 1. Crack face loading. You are correct. I don't believe the elements incident on the front have the traction applied. However, that omission will not impact the solution more that a tiny fraction of a percent given the vanishing small area of those elements. 2. Pre-processors. Post-processing of WARP3D results using the open-source ParaView code is our default go to solution and has been for 5+ years. For mesh generation, there does not exist (to my knowledge) an open-source code of the same extensive capabilities, runs on all 3 platforms, .... We use Patran and many other users adopt FEMAP. Both are commercial and have very wide use. FEMAP outputs Patran neutral files which the patwarp program in our distribution processes. These codes build complete models: geometry, meshing, loadings and boundary conditions of all types. For specialized crack models, we use FEACrack which offers WARP3D as one solution option (we have no financial relationship with the FEACrack folks). The open source code GMSH may provide some users with an adequate solution. We have a beta Python program which converts the Abaqus style *.inp file output by GMSH into a WARP3D input file. The code handles tet4, tet10, hex8 and hex20 elements. We're developing some experience with GMSH but are not sure yet that it will impose many types of loading and boundary conditions. But at least the nodal coordinates, element types, and connectivities are translated. This may be sufficient for many users. Bob — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#7 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/API4SVCALMEWC4CARSRBYFLR5WMLHANCNFSM4PHSBNGQ>.

[rhdodds]

Hi Rudy,

Update: manual_examples_chpt1/example_3_linear

This directory has been substantially updated. Please download this entire subdirectory.
The RPV has 3 loadings: (1) internal pressure w/o crack face, (2) crack face pressure, (3) quadratic temperature field over wall thickness.

There are now 3 input files to solve each loading separately: warp3d_internal_pressure.inp, warp3d_crack_face_pressure.inp, warp3d_temperarure_gradient.inp.

The domain-integration integral input is now also in 3 separate files: domain_define_internal_pressure.inp,
domain_define_face_pressure.inp, domain_define_temperature_gradient.inp

Output files of results: woutput_internal_pressure, woutput_crack_face_pressure, woutput_temperature_gradient

The J, K, T-stress results for (1) internal pressure loading, (2) crack face pressure loading agree with those included in Manual Section 1.3 tables.

The J, K, T values for temperature gradient do not agree. After a day of investigation, to include running WARP3D versions back for 5 years, it seems the Section 1.3 values listed for the temperature gradient were entered incorrectly. Code from
years ago gives same J-values as current version.

I'm updating Section 1.3 for this issue and to cleanup some text/tables than can be better.

Best,

Bob

[rudyverderber]

Hi Bob, I downloaded the new input decks from GitHub. I ran 1 and 2. These models match, for the variables checked, the original models. For 1) internal pressure only. From woutput_internal_pressure line 545 average: minimum: maximum: -0.5293E+02 -0.5299E+02 -0.5286E+02 0.1264E+03 0.1264E+03 0.1264E+03 …. T11 = -52.9 T33 = 126.4 For 2 face crack pressure only, From woutput_crack_face_pressure average: minimum: maximum: 0.8515E+01 0.8510E+01 0.8521E+01 0.2425E+01 0.2424E+01 0.2427E+01 T11=8.52 T33=2.43 From manual table 1.3.2,

…

-stress values: 15.2 MPa face pressure from I, displacement 8.5, -0.9 MPa 15.2 MPa internal pressure from I, displacement -53, -43 MPa #T† from displacement -80 to -90 MPa The first values match T11 for both cases. The second value does not match T33 in either case. (They seem close.) What am I missing? Per Rudy 7/26 (…I assume the internal pressure (ch3 ex 3&4) is on the inside surfaces (minus the flaw) and the crack face pressure is on the inside of the flaw. . I oddly suspect that the face doesn’t include the tip. ...?) Per Bob 7/27 1. Example 3 in Chpt 1. Crack face loading. You are correct. I don't believe the elements incident on the front have the traction applied. However, that omission will not impact the solution more that a tiny fraction of a percent given the vanishing small area of those elements. * Using the nodal radial location The full area is 139468 sq units The applied area is 139145 sq units The difference is 0.23% * I noticed the crack face domain command. Manual section 4.5.7.1 domain theta_0 … crack face tractions ty 15.2 I gathered it corrects the entire integrals domain for axial load. The pressure is applied to 1/3 the domain. The crack shape has a ball end. 1. If the correction is applied uniformly, then the region without the load would be incorrect. Is that correct? If yes, then is that a reason why the T33 values don’t match? 2. In order to do pressure on curved surfaced, would you need a command like, “crack face pressure {p}? Thanks, Rudy Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 From: Robert H Dodds Jr<mailto:notifications@github.com> Sent: Tuesday, July 28, 2020 9:41 PM To: rhdodds/warp3d<mailto:warp3d@noreply.github.com> Cc: rudyverderber<mailto:rudyverderber@outlook.com>; Author<mailto:author@noreply.github.com> Subject: Re: [rhdodds/warp3d] Chapter 1 examples 3 and 4 on Windows don't match manual (#7) Hi Rudy, Update: manual_examples_chpt1/example_3_linear This directory has been substantially updated. Please download this entire subdirectory. The RPV has 3 loadings: (1) internal pressure w/o crack face, (2) crack face pressure, (3) quadratic temperature field over wall thickness. There are now 3 input files to solve each loading separately: warp3d_internal_pressure.inp, warp3d_crack_face_pressure.inp, warp3d_temperarure_gradient.inp. The domain-integration integral input is now also in 3 separate files: domain_define_internal_pressure.inp, domain_define_face_pressure.inp, domain_define_temperature_gradient.inp Output files of results: woutput_internal_pressure, woutput_crack_face_pressure, woutput_temperature_gradient The J, K, T-stress results for (1) internal pressure loading, (2) crack face pressure loading agree with those included in Manual Section 1.3 tables. The J, K, T values for temperature gradient do not agree. After a day of investigation, to include running WARP3D versions back for 5 years, it seems the Section 1.3 values listed for the temperature gradient were entered incorrectly. Code from years ago gives same J-values as current version. I'm updating Section 1.3 for this issue and to cleanup some text/tables than can be better. Best, Bob — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#7 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/API4SVEPH7VCBW5QV7UCCTDR5542VANCNFSM4PHSBNGQ>.