fag


	1. Does MSU_Turbo write checkpoint files for restarting jobs after a hardware downtime?

		TURBO can write out restart files as specified by user. This parameter is called num_iter_restart_write, which defines the number of iterations before writting a restart file. Computation can be resumed after restart files are created at the point where they were written. This however, has nothing to do with machine downtime. In other words, in case of system failure the most you can recover is when the last restart files were written.

	2 How to generate the files: - cor.inlet_[steady/unsteady] - cor.exit_[steady/unsteady]

		In the design of TURBO, cor* files should be generated as post-processed results of APNASA solutions. Especially if you are trying to model the incoming wakes. These files contain flow variables at two cutting planes, usually near the exit of the upstream blades, from the APNASA solution that has either wake informations (cor.inlet.unsteady) or inlet condition (cor.inlet.steady). If you don't have a APNASA solution, you will need to find other way to generate the data and convert it to the APNASA data format. The format can be found on the TURBO website. Online Documentation > Input Files > Flow File Format
	3. How to run flutter simulation?

		To run flutter simulations, you would need to describe blade motion through a displacement file that contains the frequency, magnitude, and inter-blade phase angle of the blade motion. This displacement file is generated with a TURBO-AE pre-processor. MSU does not provide support for this pre-processor. You should contact Dr. Milind Bakhle at NASA Glenn on use and acquiring the code. His e-mail is milind.A.Bakhle@grc.nasa.gov