Solve - Revision history

Jopa6460: /* A few helpful video tutorials */

2020-09-15T04:21:44Z

‎A few helpful video tutorials

Jopa6460: /* Running the Solver */

2020-09-15T04:21:09Z

‎Running the Solver

Jopa6460: /* Running the Solver */

2020-09-15T04:13:23Z

‎Running the Solver

Jopa6460 at 03:56, 15 September 2020

2020-09-15T03:56:39Z

Jopa6460: /* Retrieve/build a version of PHASTA code */

2020-09-15T03:45:09Z

‎Retrieve/build a version of PHASTA code

Jopa6460: /* Build the executable/specify runtime parameters */

2020-09-15T03:40:45Z

‎Build the executable/specify runtime parameters

Jopa6460: /* Retrieve/build a version of PHASTA code */

2020-09-15T03:33:36Z

‎Retrieve/build a version of PHASTA code

Jopa6460: /* Retrieve/build a version of PHASTA code */

2020-09-15T03:22:23Z

‎Retrieve/build a version of PHASTA code

Jopa6460: /* Retrieve/build a version of PHASTA code */

2020-09-15T03:13:00Z

‎Retrieve/build a version of PHASTA code

Jopa6460 at 03:10, 15 September 2020

2020-09-15T03:10:58Z

← Older revision		Revision as of 04:21, 15 September 2020
Line 170:		Line 170:
	[https://fluid.colorado.edu/tutorials/CloneFromGithubAndBranch.mov CloneFromGithubAndBranch.mov ] (video)		[https://fluid.colorado.edu/tutorials/CloneFromGithubAndBranch.mov CloneFromGithubAndBranch.mov ] (video)

−	[[Tutorial_Video_Overviews#CloneFromGithubAndBranch.mov \|Video notes of CloneFromGithubAndBranch.mov ]] (link to timestamps)	+	[[Tutorial_Video_Overviews#CloneFromGithubAndBranch.mov\|Video notes of CloneFromGithubAndBranch.mov]] (link to timestamps)

← Older revision		Revision as of 04:21, 15 September 2020
Line 164:		Line 164:

	As the simulation continues it will produce successive checkpoint restart files that contain the solution data at that timestep. These and the geombc files will be what is post-proccessed in Paraview.		As the simulation continues it will produce successive checkpoint restart files that contain the solution data at that timestep. These and the geombc files will be what is post-proccessed in Paraview.
		+
		+
		+	=== A few helpful video tutorials===
		+
		+	[https://fluid.colorado.edu/tutorials/CloneFromGithubAndBranch.mov CloneFromGithubAndBranch.mov ] (video)
		+
		+	[[Tutorial_Video_Overviews#CloneFromGithubAndBranch.mov \|Video notes of CloneFromGithubAndBranch.mov ]] (link to timestamps)
		+
		+
		+
		+
		+	[https://fluid.colorado.edu/tutorials/BlancoBuidingPHASTA.mov BlancoBuidingPHASTA.mov ] (video)
		+
		+	[[Tutorial_Video_Overviews#BlancoBuidingPHASTA.mov\|Video notes of BlancoBuidingPHASTA.mov]] (link to timestamps)
		+
		+
		+
		+
		+	[https://fluid.colorado.edu/tutorials/PHASTA_workflow_RB.mkv PHASTA_workflow_RB.mkv ] (video)
		+
		+	[[Tutorial_Video_Overviews#PHASTA_workflow_RB.mkv\|Video notes of PHASTA_workflow_RB.mkv]] (link to timestamps)
		+
		+
		+
		+
		+	[https://fluid.colorado.edu/tutorials/RajDemoPrepSolvePost.mov RajDemoPrepSolvePost.mov ] (video)
		+
		+	[[Tutorial_Video_Overviews#RajDemoPrepSolvePost.mov\|Video notes of RajDemoPrepSolvePost.mov]] (link to timestamps)
		+
		+
		+
		+
		+	[https://fluid.colorado.edu/tutorials/PrepSolvePostBLandC.mp4 PrepSolvePostBLandC.mp4 ] (video)
		+
		+	[[Tutorial_Video_Overviews#PrepSolvePostBLandC.mp4\|Video notes of PrepSolvePostBLandC.mp4]] (link to timestamps)

← Older revision		Revision as of 04:13, 15 September 2020
Line 144:		Line 144:

	=== Running the Solver ===		=== Running the Solver ===
		+	Create the runPHASTA.sh in your run directory. Where you see <pathtoBuildDir> include your path to your build directory where you retrieved the input.config file. The #pconf line is an example that I have used myself, yours should look simular.
		+	#/bin/bash
		+	# VER=C or VER=IC should be specified
		+	#pconf=/users/jopa6460/git-phasta/build_JohnDev-STG_D; VER=IC
		+	pconf=<pathtoBuildDir>; VER=IC
		+
		+	date
		+	mpirun $2 -np $1 -x PHASTA_CONFIG=$pconf $pconf/bin/phasta${VER}.exe
		+	date
		+
		+
		+	Now you have everything you need to run your first PHASTA simulation! In the Run directory execute the following line:
		+	./runPHASTA.sh 8
		+	Output of a proper run of PHASTA contains information on 1)the step number the simulation is on 2) the relative residual (convergence relative to this run's initial residual), 3) various other outputs based on runtime parameters (like BC and IC info).
		+	A single time iteration with step construction 1 0 10 11 1 0 10 11 has the following output:
		+
		+	Where
		+
		+
		+	As the simulation continues it will produce successive checkpoint restart files that contain the solution data at that timestep. These and the geombc files will be what is post-proccessed in Paraview.

@@ Line 47: / Line 47: @@
   git checkout "branchname".
 If this is a branch that I will be working on for a while, I tend to alter the build and code directories according to the branch-name. Note that the respective pointer in the "unpack_buildFiles.sh" file (ie the last line) will have to be set accordingly.
 === Running the Solver ===

@@ Line 38: / Line 38: @@
 This should create the makefiles required for the build. Perform the following command:
   make -j
+The following means that you executable has been built:
+ Built target phastaIC.exe

@@ Line 13: / Line 13: @@
   git clone https://github.com/PHASTA/phasta-next.git
 After this is finished their will be a subdirectory created named phasta-next that contains the code tree that you wish to build.
-Back within the git-phasta directory create another subdirectory named: "build_phasta-next".
+Back within the git-phasta directory create another subdirectory named: "build_phasta-next". Now we must set the environment so that the compiler has the necessary libraries. If you perform the following command, the listed environment libraries that ken often uses are listed, and are often sufficient:
 ===== Additional notes =====

@@ Line 10: / Line 10: @@
 Navigate to your home directory. Create a directory here named "git-phasta". In a web browser, navigate to the online git repository for phasta-next and select the "clone" or "code" icon. The result should be the simular to the following picture, where a pop-up gives a web address:
   [[File:GitClone.png]]
+===== Additional notes =====
-Within this directory create one subdirectories named "phasta-next" and "build_phasta-next".
+If there is a specific branch off of phasta-next that you'd like to build, navigate to phasta-next and use the following command:
 === Running the Solver ===

@@ Line 7: / Line 7: @@
 === Build the executable/specify runtime parameters===
 What remains is to determine the version of PHASTA to build and run. Since there are a bunch of researchers working on PHASTA at any given time, there are many branches/versions of the main code. If you are a part of the research cohort you may be directed to phasta-next, but many of the same steps may be taken from the public version.
-==== Retrieve/build a version of PHASTA code ===
+==== Retrieve/build a version of PHASTA code ====
 Navigate to your home directory. Create a directory here named "git-phasta". In a web browser, navigate to the online git repository for phasta-next. Within this directory create one subdirectories named "phasta-next" and "build_phasta-next".
-[[File:
+[[File:GitClone.png]]
 === Running the Solver ===