Remeshing, Amazon EC2, Convergence Criteria, Export
1. While meshing, Caedium creates the full mesh and then goes on to remesh at a significantly lesser speed of around 200tets/sec. This happens with a mesh of 1m million tets while running on a amazon EC2 cluster (26 core, 68GB ram) but not in my colleague's laptop. (same caedium settings) [both trial versions]
2. Do you have any recommendations on how to optimise Caedium to run on a Amazon EC2 Windows cluster of 26 EC units (8cores) and 68GB (using 100% CPU, but only 6GB RAM for simulations). More specifically : should I use parallel config as 'shared memory' or 'cluster' . If so, are processes/cores 8 or 26 ?.
I've run a simulation of 0.3 million cells in 20 mins (no issues with remeshing either), but same geomtery of 0.6million cell took 6 hours on the same machine. Haven't run the simulation for 1million cells as yet due to remeshing issues.
Also, I'm planning to buy a 1year subscription to Caedium. What license(/s) would you suggest if I'm to run Caedium on a Amazon EC2 instance (26 cores, 68GB ram ).
3. Where can I change convergence criteria ?
4. I'm unable to save/export if I interrupt/pause the simulations before hitting the max number of iterations specified. The message received is something like ' Interrupted: unable to save file ............. .case '.
5. How can I normalize lift and drag values to output Cl and Cd.
Sorry for any ignorance and hope I've expressed my queries clearly.