I'm trying to learn about OpenFOAM Computational Fluid Dynamics software in order to use it for my undergraduate thesis. I am currently following Joszef Nagy's tutorial to run your first simulation. Everything up to about the 18:30 mark has worked completely fine. Editing initial conditions, timestep, savestep, total run time, and so on have all worked without a hitch. I have navigated to the correct directory, which in his video is /OpenFOAM/OpenFOAM-2.3.0/tutorials/incompressible/icoFoam/elbow_tri but on my installation my path goes /opt/openfoam8/tutorials... and the rest. I first tried to run the command as it was given in the video, which is
fluentMeshToFoam elbow.msh
And the command worked just fine, up until the point it needed to write the changes to constant/polymesh, at which point it gave the error
FOAM FATAL ERROR:
The parent directory does not allow write permission to the process,
or one of the directories in "/opt/openfoam8/tutorials/incompressible/icoFoam/elbow_tri/constant/polyMesh" did not allow search (execute) permission.
From function bool Foam::mkDir(const Foam::fileName&, mode_t)
in file POSIX.C at line 346.
So what i understand happened is it succeeded in creating the mesh, but didn't have the proper permissions to write the mesh file to the constant/polyMesh folder.
With this in mind, I instead tried the command
sudo fluentMeshToFoam elbow.msh
But this time i was given the much shorter error
FOAM FATAL ERROR :
Could not find mandatory etc entry (mode=ugo)
'controlDict'
But, this time, it didn't even go through the mesh creation process. I was given this error right out of the gate. Can someone who is familiar with OpenFOAM explain why this is happening? I have had a LOT of problems even trying to get this software installed on my computer, so I'm getting very frustrated at this point and can hardly think straight.
Thanks so much.
NB: I am running Ubuntu version 20.04 LTS and OpenFOAM version 8.
This, and several other problems, can be resolved by running OpenFOAM from the correct folder. After you have installed OpenFOAM, be sure to make a folder in your home directory called OpenFOAM with a sub folder called run, as detailed on their website. To run a tutorial case, copy it from the tutorials folder in your installation and move it to this run folder and run it from there.
RUNNING OPENFOAM CASES DIRECTLY FROM THE INSTALLATION FOLDER IS A RECIPE FOR DISASTER. DO NOT DO IT.
Related
I recently picked up the BBB I have from some time ago (the Debian image is quite old) and have been following a book on my journey. I'm relatively new to embedded electronics.
Now, I'm having trouble with running Cloud9 on my BBB, and I can't find anyone with the same issue:
I can create files and restart the workspace, but whenever I click on "run", I get the following messages:
SIOCADDRT: File exists
Also, a small error message appears for a second, and it says the following:
set option aggressive-resize -> on
After that, all of my files are stopped for run time. I do want to note, that I can run all of the .js files in the terminal that I can open in Cloud9 and that works perfectly fine.
I'm really not sure as to what is causing this. When I check the web page itself, I get the following errors:
Disregard terminal: output203990
XML Parsing Error: no root element found
Location: http://192.168.7.2:3000/vfs/1/9cmZHC5eYxOHaB7N/workspace///tab2?access_token=token
Line Number 1, Column 1:
It seems like the BBB is having trouble communicating between Cloud9 and its own self. I have tried 2 browsers--Firefox and Edge. If anyone else has encountered the same problem or could suggest a possible fix without me loading a new image onto the board (which would be the ultimate solution), that'd be helpful!
I'm not sure what the issue was, but flashing a newer Debian image got rid of the problem.
I just barely installed Code::Blocks so that I can learn how to program in fortran with a real IDE (with debugging and other fun things). But I'm running into a puzzling problem while trying to get it to work--Code::Blocks seems to be unable to create any files at all.
Info: I'm running Linux Mint 17 and built Code::Blocks from source (version 13.12 for Debian, which seemed like the closest I could get). When I try to create a new project, it gives the following error for every single file in the project:
Warning
Couldn't save project path/filename
(Maybe the file is write-protected?)
This is when I run code::blocks from the terminal as a super user. When I simply run Code::Blocks without super user, I get the following:
Error
Couldn't create the project directory
path/
No idea what's going on here, and I can't find a similar question. Help?
I finally found the answer.
Do not create new file or new project in C
Try to create in other disks.
Folders situated in C are protected folders
and you can save your file or save as file just fine
I was facing the same problem but after following this below procedure I was able to run the program
Procedure:
In code-block go to the Setting, click on Tool chain executable then click on auto detect
This will solve the problem
One possible cause for your problem is that you specified an invalid path to a new project when starting one.
If you see "Invalid file path" in the "Resulting filename field", you generally should not hit "Next".
Below is a screenshot showing how your dialog should look when you've filled in the file path properly:
In case anyone is curious, I overlooked this initially in CodeBlocks 17.2 on Windows 10 before finding this question and posting this answer.
Linux mint 19.1 with a fresh install of Code::Blocks 16.01.
I was getting the same message as below when trying to create a project and the dialog box never showed the "invalid path" message.
"Couldn't create the project directory: /home/mydir/Code/CppTraining/HelloWorld/"
I found I was able to create the path after I removed one level of subfolders. It seems code::blocks doesn't like project paths to have more than one or two levels of subfolders?
If you're flipping back and forth from Linux to Windows, this problem may occur and it's extremely frustrating as a Linux user to debug.
Windows doesn't understand that the tilde "~/" means your home folder, so you actually have to type "C:\Users\<yourusername>\<path>"
, instead of just typing "~/<path>"
Hope this helps anyone that has run into this.
I have a project that I am building using cygwin as an env. This weekend, I tried to do a standard git pull, one that has worked hundreds of times before, and I get this message.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
/usr/bin/ssh.exe: error while loading shared libraries: cygssp-0.dll: cannot open shared object file: No such file or directory
I'm a bit confused since this has never happened before. I googled "cygssp-0.dll" and found that it is some .dll file, specifically I looked here.
I tried the first option, and got to this step
enter "regsvr32 /u cygssp-0.dll" in the command line
and I got the message
The module "cygssp-0.dll" failed to load.
Make sure the binary is stored at the specific path or debug it to check for problems with the binary or dependent .DLL files.
The specific module could not be found.
At this point, I am thoroughly confused, and not all too keen to start reinstalling windows just yet. I've tried re installing cygwin.. does anybody have any ideas on what to do?
EDIT : I have already attempted to run setup-x86_64.exe several times, in an attempt to re-install something from the cygwin side.
Turn your antivirus off of silent mode or turn off heuristics. It's just deleting the file without telling you. libssp is getting deleted because it's a security library that does things to the call stack that antivirus programs don't like. (Specifically, it adds canaries, random values inserted into the stack that are meant to guard against some buffer overflow attacks. However, an antivirus that isn't coded to handle stack canary insertion will see it as a buffer overflow attack itself.)
Had the same issue today while trying to do push via Cygwin's git via ssh.
The solution is to reinstall or update Cygwin, as missing library will be redownloaded and put in proper place. Be sure that your antivirus software isn't removing it again, so disable everything that might delete it, and/or whitelist cygssp-0.dll location. As of today they're located under:
cygwin_root\bin\cygssp-0.dll
cygwin_root\usr\i686-pc-cygwin\sys-root\usr\bin\cygssp-0.dll
(second path only for 64 bit distribution of Cygwin)
I'm trying to install/configure FishEye as per the instructions on Atlassian's website, but either the web server for the install doesn't start properly (and I see multiple exception message in the command window), or I get a 503 Response code when I try to access the installation link.
How can I get past this?
The installation instructions currently aren't clear, especially on a Windows environment.
Here's what you need to do (in my case on a Windows system).
Extract the fisheye archive to the directory where you're intending to run Fisheye from. (on my system, I made this <drive>:\Atlassian\FishEye).
Create a directory for your data. (I made this <drive>:\Application Data\FishEye)
Create an environment variable (Window System Variable) named 'FISHEYE_INST' and set it to the path you created in Step 2. ('INST' in this case means instance and not installation folder.
Copy the 'config.xml' file from <extracted_archive> to your FISHEYE_INST folder.
Open a command prompt and run the <extracted archive>\bin\run.bat file. (ie :\Atlassian\FishEye\bin\run.bat).
The online documentation is a little misleading at this point. They indicate that you run 'start.bat', which won't work (or at least, it wouldn't work for me...)
Open a browser and point it to 'http://localhost:8060'.
Following the steps above let me get FishEye up and running without any further issues.
I'm having a problem getting started with compass/sass. I eventually managed to install compass, although I had to google around because the instructions on the compass website didn't work for me.
Next step was to create a project. I thought this would be simple enough by typing:
$ compass create path/to/project --using blueprint/basic --sass-dir=sass --css-dir=css
Unfortunately, this didn't work. The first thing to fail was that it told me that --using was not a recognised command (even though that is exactly what it tells you to type in the compass installation instructions). So, I tried creating the project taking away all three of the additional options.
This did create a project, although not in the place I specified. Rather than placing it in path/to/project it created the files and directories straight into my home folder ie /Users/me/
I must be doing something wrong, I can't believe that a tool designed to save time and make life easier could be so difficult to get up and running. I'm not great at using the command line, but I am able to follow instructions!
Any pointers would be appreciated!
It sounds like your running compass v0.8, please upgrade to v0.10 and that command will work.