PubInv / PubInv/EcoPot

Rob can't run icoFoam in hotfluidheater....

Open
#6 1 comment 0 reactions 1 assignee View on GitHub

@Cledito-Delta is already working on this.

Since Sep 30, 2024.

Dominant language
C++
Stars
1
Forks
2
PR merge metrics
No merged PRs in 30d

Description

ubuntu@openfoam2:~/EcoPot/OpenFOAM/hotfluidheater$ icoFoam
/---------------------------------------------------------------------------
| ========= | |
| \ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \ / O peration | Version: v2012 |
| \ / A nd | Website: www.openfoam.com |
| \/ M anipulation | |
*---------------------------------------------------------------------------*/
Build : _b12839ff-20220610 OPENFOAM=2012 patch=220610
Arch : "LSB;label=32;scalar=64"
Exec : icoFoam
Date : Sep 30 2024
Time : 12:01:10
Host : openfoam2
PID : 127686
I/O : uncollated
Case : /home/ubuntu/EcoPot/OpenFOAM/hotfluidheater
nProcs : 1
trapFpe: Floating point exception trapping enabled (FOAM_SIGFPE).
fileModificationChecking : Monitoring run-time modified files using timeStampMaster (fileModificationSkew 5, maxFileModificationPolls 20)
allowSystemOperations : Allowing user-supplied system call operations

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time

Create mesh for time = 0

PISO: Operating solver in PISO mode

Reading transportProperties

--> FOAM FATAL ERROR: (openfoam-2012 patch=220610)
cannot find file "/home/ubuntu/EcoPot/OpenFOAM/hotfluidheater/constant/transportProperties"

From virtual Foam::autoPtr<Foam::ISstream> Foam::fileOperations::uncollatedFileOperation::readStream(Foam::regIOobject&, const Foam::fileName&, const Foam::word&, bool) const
in file global/fileOperations/uncollatedFileOperation/uncollatedFileOperation.C at line 547.

FOAM exiting

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.