<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://fluid.colorado.edu/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Kylew</id>
		<title>PHASTA Wiki - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://fluid.colorado.edu/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Kylew"/>
		<link rel="alternate" type="text/html" href="https://fluid.colorado.edu/wiki/index.php/Special:Contributions/Kylew"/>
		<updated>2026-04-26T23:07:42Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.30.0</generator>

	<entry>
		<id>https://fluid.colorado.edu/wiki/index.php?title=Janus_Proposals&amp;diff=474</id>
		<title>Janus Proposals</title>
		<link rel="alternate" type="text/html" href="https://fluid.colorado.edu/wiki/index.php?title=Janus_Proposals&amp;diff=474"/>
				<updated>2014-02-05T21:20:23Z</updated>
		
		<summary type="html">&lt;p&gt;Kylew: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Before writing proposal, visit [https://www.rc.colorado.edu/policies/applicationguidelines Application Guidelines] and [https://www.rc.colorado.edu/allocationcycles Allocation Cycles] to review procedure guidelines.  All new users are advised to apply for a testing allocation of 50,000 cpu hours (SU's) before submitting a proposal for a medium or large allocation.  Testing allocations are granted almost immediately and require very little work. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Writing the Proposal ==&lt;br /&gt;
&lt;br /&gt;
It is suggested that new users look to previously submitted proposals as a template.  Previous proposals can be found here:&lt;br /&gt;
&lt;br /&gt;
  /projects/janus_proposals/Proposals/&lt;br /&gt;
&lt;br /&gt;
Only section 1, 2, 6, and 7 need to be changed to fit the user's proposal.  Estimation of cpu hours and data storage needed should be based off of previous experience found using the testing allocation.  Section 5 should be updated if possible by checking to see if new papers citing Janus have been written.  Check the following directory before submitting proposal:&lt;br /&gt;
&lt;br /&gt;
  /projects/janus_proposals/Papers/&lt;br /&gt;
&lt;br /&gt;
The list of papers or conference proceedings which acknowledge Janus is the following:&lt;br /&gt;
&lt;br /&gt;
  M. Rasquin, C. Smith, K. Chitale, S. Seol, B.A. Matthews, J.L. Martin, O. Sahni, R.M. Loy, M.S. Shephard, K.E. Jansen.&lt;br /&gt;
  Scalable fully implicit finite element flow solver with application to high-fidelity flow control simulations on a realistic wing design.&lt;br /&gt;
  Submitted to Computing in Science and Engineering in January 2014.&lt;br /&gt;
  Janus usage: Mesh generation, Mesh partitioning.&lt;br /&gt;
&lt;br /&gt;
  K. Chitale, M. Rasquin, O. Sahni, M. Shephard, K. Jansen. &lt;br /&gt;
  Anisotropic Boundary Layer Adaptivity of Multi-Element Wings. &lt;br /&gt;
  AIAA Science and Technology Forum and Exposition Conference; National Harbor, MA, USA; January 13-17, 2014.&lt;br /&gt;
  Janus usage: Mesh generation, Mesh partitioning, Mesh adaptation, PHASTA simulation.&lt;br /&gt;
&lt;br /&gt;
  K. Chitale, M. Rasquin, J. Martin, K. Jansen. &lt;br /&gt;
  Simulations of EUROLIFT DLR-F11 wing with a finite element solver. &lt;br /&gt;
  AIAA Science and Technology Forum and Exposition Conference; National Harbor, MA, USA; January 13-17, 2014.&lt;br /&gt;
  Janus usage: Mesh generation, Mesh partitioning, Mesh adaptation, PHASTA simulation.&lt;br /&gt;
&lt;br /&gt;
  K. Chitale, O. Sahni, S. Tendulkar, R. Nastasia, M. Shephard, K. Jansen. &lt;br /&gt;
  Boundary Layer Adaptivity for Transonic Turbulent Flows.&lt;br /&gt;
  AIAA Computational Fluid Dynamics Conference; San Diego, CA, USA; June 24-27, 2013.&lt;br /&gt;
  Janus usage: Mesh generation, Mesh partitioning, Mesh adaptation, PHASTA simulation.&lt;br /&gt;
&lt;br /&gt;
  X. Dechamps, M. Rasquin, K.E. Jansen and G. Degrez. &lt;br /&gt;
  Numerical study of turbulent pipe flow with transverse magnetic field using a spectral/finite element solver. &lt;br /&gt;
  AIAA Plasmadynamics and Lasers Conference, San Diego, CA, USA; June 24-27, 2013.&lt;br /&gt;
  Janus usage: SFELES simulation.&lt;br /&gt;
&lt;br /&gt;
After the proposal has been submitted, please add it to the Janus proposal directory with the previously submitted proposals.&lt;/div&gt;</summary>
		<author><name>Kylew</name></author>	</entry>

	<entry>
		<id>https://fluid.colorado.edu/wiki/index.php?title=Janus_Proposals&amp;diff=463</id>
		<title>Janus Proposals</title>
		<link rel="alternate" type="text/html" href="https://fluid.colorado.edu/wiki/index.php?title=Janus_Proposals&amp;diff=463"/>
				<updated>2014-02-04T23:46:09Z</updated>
		
		<summary type="html">&lt;p&gt;Kylew: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Before writing proposal, visit [https://www.rc.colorado.edu/policies/applicationguidelines Application Guidelines] and [https://www.rc.colorado.edu/allocationcycles Allocation Cycles] to review procedure guidelines.  All new users are advised to apply for a testing allocation of 50,000 cpu hours (SU's) before submitting a proposal for a medium or large allocation.  Testing allocations are granted almost immediately and require very little work. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Writing the Proposal ==&lt;br /&gt;
&lt;br /&gt;
It is suggested that new users look to previously submitted proposals as a template.  Previous proposals can be found here:&lt;br /&gt;
&lt;br /&gt;
  /users/kylew/Janus/Proposals/&lt;br /&gt;
&lt;br /&gt;
Only section 1, 2, 6, and 7 need to be changed to fit the user's proposal.  Estimation of cpu hours and data storage needed should be based off of previous experience found using the testing allocation.  Section 5 should be updated if possible by checking to see if new papers citing Janus have been written.  Check the following directory before submitting proposal:&lt;br /&gt;
&lt;br /&gt;
  /users/kylew/Janus/Papers/&lt;br /&gt;
&lt;br /&gt;
After the proposal has been submitted, please add it to the Janus proposal directory with the previously submitted proposals.&lt;/div&gt;</summary>
		<author><name>Kylew</name></author>	</entry>

	<entry>
		<id>https://fluid.colorado.edu/wiki/index.php?title=Janus_Proposals&amp;diff=462</id>
		<title>Janus Proposals</title>
		<link rel="alternate" type="text/html" href="https://fluid.colorado.edu/wiki/index.php?title=Janus_Proposals&amp;diff=462"/>
				<updated>2014-02-04T23:36:39Z</updated>
		
		<summary type="html">&lt;p&gt;Kylew: /* Writing the Proposal */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Overview ==&lt;br /&gt;
&lt;br /&gt;
Before writing proposal, visit [https://www.rc.colorado.edu/policies/applicationguidelines Application Guidelines] and [https://www.rc.colorado.edu/allocationcycles Allocation Cycles] to review procedure guidelines.  All new users are advised to apply for a testing allocation of 50,000 cpu hours (SU's) before submitting a proposal for a medium or large allocation.  Testing allocations are granted almost immediately and require very little work. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Writing the Proposal ==&lt;br /&gt;
&lt;br /&gt;
It is suggested that new users look to previously submitted proposals as a template.  Previous proposals can be found here:&lt;br /&gt;
&lt;br /&gt;
  /users/kylew/Janus/Proposals/&lt;br /&gt;
&lt;br /&gt;
Only section 1, 2, 6, and 7 need to be changed to fit the user's proposal.  Estimation of cpu hours and data storage needed should be based off of previous experience found using the testing allocation.  Section 5 should be updated if possible by checking to see if new papers citing Janus have been written.  Check the following directory before submitting proposal:&lt;br /&gt;
&lt;br /&gt;
  /users/kylew/Janus/Papers/&lt;/div&gt;</summary>
		<author><name>Kylew</name></author>	</entry>

	<entry>
		<id>https://fluid.colorado.edu/wiki/index.php?title=Janus_Proposals&amp;diff=461</id>
		<title>Janus Proposals</title>
		<link rel="alternate" type="text/html" href="https://fluid.colorado.edu/wiki/index.php?title=Janus_Proposals&amp;diff=461"/>
				<updated>2014-02-04T23:34:38Z</updated>
		
		<summary type="html">&lt;p&gt;Kylew: Janus Proposal Writing&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Overview ==&lt;br /&gt;
&lt;br /&gt;
Before writing proposal, visit [https://www.rc.colorado.edu/policies/applicationguidelines Application Guidelines] and [https://www.rc.colorado.edu/allocationcycles Allocation Cycles] to review procedure guidelines.  All new users are advised to apply for a testing allocation of 50,000 cpu hours (SU's) before submitting a proposal for a medium or large allocation.  Testing allocations are granted almost immediately and require very little work. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Writing the Proposal ==&lt;br /&gt;
&lt;br /&gt;
It is suggested that new users look to previously submitted proposals as a template.  Previous proposals can be found here:&lt;br /&gt;
&lt;br /&gt;
  /users/kylew/Janus/Proposals/&lt;br /&gt;
&lt;br /&gt;
Only section 1, 2, 6, and 7 need to changed to fit the user's proposal.  Estimation of cpu hours and data storage needed should be based off of previous experience found using the testing allocation.  Section 5 should be updated if possible by checking to see if new papers citing Janus have been written.  Check the following directory before submitting proposal:&lt;br /&gt;
&lt;br /&gt;
  /users/kylew/Janus/Papers/&lt;/div&gt;</summary>
		<author><name>Kylew</name></author>	</entry>

	</feed>