## 7.1. Where are my AWS credentials stored locally?#

Your AWS credentials are encrypted and stored locally (if you hit Yes previously at authentication step) at

~/.flow360/


## 7.2. How to check my mesh processing status?#

To list all your mesh files:

>>> flow360client.mesh.ListMeshes()


To view one particular mesh:

>>> flow360client.mesh.GetMeshInfo('')


## 7.3. My case is still running, but how can I check the current residual and surface force result?#

>>> caseResid = flow360client.case.GetCaseResidual('')


## 7.4. How do I download or view a finished case result?#

>>> flow360client.case.DownloadSurfaceResults('', '/tmp/surfaces.tar.gz')


Replace the second parameter with your target location and output file name, ending with ‘.tar.gz’.

>>> flow360client.case.DownloadVolumetricResults('', '/tmp/volume.tar.gz')


## 7.5. How can I delete my mesh or case?#

To delete a mesh:

>>> flow360client.mesh.DeleteMesh('')


To delete a case:

>>> flow360client.case.DeleteCase('')


Danger

You won’t be able to recover your deleted cases or mesh files including its results after your deletion.

## 7.8. Does FlexCompute charge for data storage?#

For some data storage we do not charge, but for some data we do. See details:

resource

storage type

storage price

surface mesh

free

volume mesh

free

case

standard

0.05 FlexUnit/GB/month

archived

0.005 FlexUnit/GB/month

Warning

The minimum archived data cost is 6 months. Archiving operation is fast, but restoring can take up to 48 hours. When you restore your data from archive before the six month period, you will see a pro-rata charge added to your transaction history for the remaining period.

To reduce data storage costs we encourage to:

1. Delete case if results will no longer be needed.

3. Archive case to reduce storage costs by 10x and still be able to revisit the case in the future.

## 7.9. What is storage type?#

We have two storage types: standard and archived. You can check storge type for each case next to the storage size on the case table view:

Standard storage allows for all operations: retry case, fork case, download all results including surface results and volumetric results.

Archived storage disables these operations: fork case, retry direct child case, download surface and volume results.

## 7.10. How can I archive my case?#

You can only archive a case with status completed and storage type standard.

To archive an individual case follow these steps:

1. Go to client.flexcompute.com.

2. Navigate to case you want to archive

3. From action list click archive button:

1. You will see the following window with details about archiving operation:

Warning

The minimum archived data cost is 6 months. Archiving operation is fast, but restoring can take up to 48 hours. When you restore your data from archive before the six month period, you will see a pro-rata charge added to your transaction history for the remaining period.

1. Select “Archive”. The icon next to storage size will change:

1. Archiving usually takes up to few minutes. When done, the storage type becomes archived.

## 7.11. How can I restore my archived case?#

1. Go to client.flexcompute.com.

2. Navigate to case you want to restore

3. From action list click restore button:

1. You will see the following window with details about restoring operation:

Warning

When you restore your data from archive before the six month period, you will see a pro-rata charge added to your transaction history for the remaining period.

1. Select “Restore”. The icon next to storage size will change:

1. Restoring takes up to 48 hours. When done, the storage type becomes standard.

## 7.12. I have many cases, how can I archive all of them at once?#

Contact support@flexcompute.com

## 7.13. 1st vs 2nd order CFD runs?#

If you look at most Flow360.json files you will see something like:

{
"navierStokesSolver" : {
"orderOfAccuracy" : 1 or 2
},
"turbulenceModelSolver" : {
"orderOfAccuracy" : 1 or 2
}
}


This dictates whether the code will run its algorithms using 1st or 2nd order interpolation in space. 1st order accuracy is much faster and much more robust than 2nd order accuracy, but nowhere near as accurate.

For time-accurate runs where we have rotating components we recommend to first run 1 revolution using “orderOfAccuracy” : 1 to help establish the flow. Then follow that with however many 2nd order accurate revolutions are needed for the flow to properly establish itself and for the forces to stabilize. Please note that if you have some parts of your vehicle downstream of your propellers it may take many revolutions for the propeller’s wake to reach the downstream geometry components.

If you want to speed things up you can run a first set of 2nd order accurate revolutions with a larger time step to help the flow establish itself quicker and then do a more precise, better converged, 2nd order run with smaller time steps to get more accurate forces. This is easily done in Flow360 through our “fork” functionality that launches a new child case using the flow solution of the parent case as the initial condition.

Also, for 1st order simulations we recommend using the following “timeStepping” values:

"maxPseudoSteps" : 12,
"CFL" : {
"initial" : 1,
"final" : 1000,
"rampSteps" : 10 (i.e., rampSteps is 2 steps less then maxPseudoSteps)
}


For 2nd order simulations we recommend using the following “timeStepping” values:

"maxPseudoSteps" : 35,
"CFL" : {
"initial" : 1,
"final" : 1e7,
"rampSteps" : 33 (i.e., rampSteps is 2 steps less then maxPseudoSteps)
}


These are just guidelines to get you started and will most likely need to be revised for your specific cases.

## 7.14. Mesh Error: Distance between 2 nodes on ring is wrong! What does this mean?#

When doing a mesh with a rotation interface, if you get a mesh processor error that looks like this:

Distance between 2 nodes on ring is wrong!
The distance from first to last = 2.5959001398487129e+02 (as reference)
But the distance = 2.7487841069926304e+02 between 2 nodes:.......


This means that your rotation interface grid does not satisfy the Flow360 concentricity requirements.

The rotation interface needs to be a body of revolution (e.g., sphere, cylinder, etc.) which encloses the entire rotating geometry. The grid points on the rotation interface can not be arbitrary. It is mandatory that they form a set of concentric rings.

The grid points on the rotation interface shown in the figure above do not satisfy the concentricity requirement. Certain points deviate slightly from a perfectly concentric circle.

This figure shows a slightly different grid that does satisfy the concentricity requirement. Notice how all the nodes are on concentric circles.

The reason for this requirement is that it greatly speeds up the interpolation process. Since this interpolation happens twice for every interface node (inner and outer domain) and for every pseudo-timestep, already knowing where the neighbors are without having to run a search algorithm every time to find the closest node is very efficient.

## 7.15. How do I create a rotating interface with concentric mesh rings?#

For your own cases, knowing that we have this concentric mesh requirement, the easiest way to create the meshes for the interface regions is to do it programmatically. We have a lot of scripts to generate various body of revolution interface shapes that will allow you to generate an interface region no matter what your geometry. Just contact us and we will help you get setup with the scripts you need.

For plain cylindrical or spherical interfaces we also have pre-generated interfaces in CGNS format ready for you to download from this link. You will notice that they come in various height to radius ratios as well as various resolutions. You will need to choose the version that best fits your needs and then rotate/scale the imported mesh to align the interface around your geometry.

## 7.16. What does the “VelocityRelative” mean in the volumeOutput of the case configuration?#

In a rotational domain, the absolute velocity, $$\overrightarrow{\boldsymbol{U}}_\text{absolute}$$, of each fluid element could be treated as the summation of a relative velocity, $$\overrightarrow{\boldsymbol{U}}_\text{relative}$$, and a velocity due to the rotating frame, $$\overrightarrow{\Omega}\times \overrightarrow{r}$$. The “VelocityRelative” means the $$\overrightarrow{\boldsymbol{U}}_\text{relative}$$:

(7.16.1)#$\overrightarrow{\boldsymbol{U}}_\text{absolute} = \overrightarrow{\boldsymbol{U}}_\text{relative} + \overrightarrow{\Omega}\times \overrightarrow{r}$

It should be noted that the above relative velocity is zero on any no-slip walls within rotational blocks.