Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • melissa melissa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 35
    • Issues 35
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • melissa
  • melissamelissa
  • Issues
  • #80

Closed
Open
Created Dec 21, 2020 by Christoph Conrads@cconradsOwner

Fix Code_Saturne setup

Code_Saturne error message:

System error: File exists

../../../code_saturne-6.0.5/src/fvm/fvm_to_melissa.c:355: Fatal error.

Error creating Melissa writer: "results":
only one Melissa server may be used, and is already used by
writer: "joining".

Code_Saturne developer response from Code_Saturne issue #77, cf. issue #73 (closed):

Hello,

This is actually related to the fact that "auxiliary" writers use the same format as the "main" writer, and as explained in the error message, only one Melissa server is actually possible. Using multiple Melissa servers would require that Melissa propose a feature/API option to connect to separate separate servers from the same code, which does not seem to be the case in the present API. So this is a Melissa issue, not a code_saturne one.

In your case, I assume that you have a joining or periodicity mesh pre-processing step activated, given the error message. Using the default visualization level, a writer is used to check the correct joining. The joining info preprocessed here carries no physical field information so is not releveant for Melissa.

There are 2 possible setting solutions here:

  • lower the visualization level for mesh joining (set it to zero)
    • an even better solution is to run the preprocessing in a separate step, and use the mesh_output (with no additional preprocessing for the CFD computation).
  • do not set the type of the main (results) writer to Melissa, but add a separate writer, and associate post-processing meshes to that writer instead of "results" (though using both is possible).
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking