https://linen.dev logo
okay as of now I have the following set up in open...
# programming
t
okay as of now I have the following set up in openFoam with regards to file overview: case ├ system,constant,0,1,2,... etc └ solutionSet ├ solution1,solution2,solution3... etc └ solutionX (X dummy index) ├ constant,system (copys from main case) ├ .foam file for paraview └ '1' file, which is a direct copy of the converged result of the main case file i.e. the final time step after convergence the thing Id like someone else to think with me a little: Right now, i have a nice solutionSet from which i can view all the solutions, however, for the true algorithm (which is yet to be implemented via python) I need both a solution set and a deflation set. The solution set is the set of all true solutions to the problem which is a subset of the deflation set. The deflation set is the set of values which have to be read by the openfoam solver to do the correct mathematical operation, the distinction between if a solution has to be added to either the deflation set, the solution set, or both, is dependent on the yet to be implemented python algorithm. For the solution set I am right now saving the entire final time step file so this is able to be viewed in paraview, however this is ofcourse very inefficient if i do the same for the deflation set as well because i do not need to see this ever and it is inefficient to save these whole directories again. Now all I need really for the openFoam algorithm is one particular volScalarField (beta) for the deflation set. Any ideas on how to efficiently save these? my current idea was to create another directory next to solutionSet called deflationSet and in this just dump all the txt files of the beta fields and let my openFoam solver read it from here directly? And then the current idea is to now try and get a python script running to handle the algorithm for distinction betweenn solutionSet and deflationSet to subsequently save all the files as previously indicated and run / clean the case?