Skip to content

Some problems in Example.ALM case #112

@TigrisZhu

Description

@TigrisZhu

Hi guys, I met some confusing problems when I was trying to run the ./runscript.solver.1 in example ALM case, which can be seen as follows.
The log.1.windPlantSolver.ALM is attached in files.
log.1.windPlantSolverALM.txt
error1

PIMPLE: Operating solver in PISO mode
Starting time loop
[4] 
[4] 
[4] --> FOAM FATAL ERROR: 
[4] index -1 out of range 0 ... 1142667
[4] 
[4]     From function UList<T>::checkIndex(const label)
[4]     in file /home/bzhu817/OpenFOAM/OpenFOAM-2.4.0/src/OpenFOAM/lnInclude/UListI.H at line 109.

error2

FOAM parallel run aborting
[7] 
[3] #0  [4] #0  [2] #0  [5] #0  [0] #0  [7] #0  Foam::error::printStack(Foam::Ostream&)Foam::error::printStack(Foam::Ostream&)Foam::error::printStack(Foam::Ostream&)Foam::error::printStack(Foam::Ostream&)Foam::error::printStack(Foam::Ostream&)Foam::error::printStack(Foam::Ostream&) at ??:?
 at ??:?
 at ??:?
[3] #1   at ??:?
 at ??:?
[5] #1  Foam::error::abort()Foam::error::abort()[4] #1  Foam::error::abort()[0] #1  [7] #1  Foam::error::abort()Foam::error::abort() at ??:?
[2] #1  Foam::error::abort() at ??:?
[5] #2   at ??:?
Foam::Ostream& Foam::operator<< <Foam::error>(Foam::Ostream&, Foam::errorManip<Foam::error>)[3] #2  Foam::Ostream& Foam::operator<< <Foam::error>(Foam::Ostream&, Foam::errorManip<Foam::error>) at ??:?
[2] #2  Foam::Ostream& Foam::operator<< <Foam::error>(Foam::Ostream&, Foam::errorManip<Foam::error>) at ??:?
[0] #2  Foam::Ostream& Foam::operator<< <Foam::error>(Foam::Ostream&, Foam::errorManip<Foam::error>) at ??:?
[4] #2  Foam::Ostream& Foam::operator<< <Foam::error>(Foam::Ostream&, Foam::errorManip<Foam::error>) at ??:?
[7] #2  Foam::Ostream& Foam::operator<< <Foam::error>(Foam::Ostream&, Foam::errorManip<Foam::error>) at ~/OpenFOAM/OpenFOAM-2.4.0/src/OpenFOAM/lnInclude/errorManip.H:85 (discriminator 4)

I achieved the boundary data through following the instructions in issue26 and then run the runscript.preprocess successfully. Before run the solve.1, I also double check all the log files to make sure that the results from the runscript.preprocess is correct. Furthermore, I also check the files which are used in runscript.preprocess and revised them partly to satisfy my case.
By the way, the wind direction in my case is 225°(southwest), and so I selected the changeDictionaryDict.updateBCs.southwest to update the boundary conditions and induced the setUp in this file. The boundary data includes 2 folders (west and south), each folder includes 60001-62000 2000 files(U T k) and faces, points and vertices.
Have you met some similar problems before? I would feel so appreciated if you can provide some suggestions about these problems. Thanks so much!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions