|
[Sponsors] |
reconstructPar --> fileName::stripInvalid() called for invalid fileName commandtouse |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
December 24, 2015, 16:46 |
|
#21 | |||
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,981
Blog Entries: 45
Rep Power: 128 |
Quote:
|
||||
May 18, 2016, 15:29 |
|
#22 |
Senior Member
Lucky
Join Date: Apr 2011
Location: Orlando, FL USA
Posts: 5,759
Rep Power: 66 |
I ran into this error today and have been tinkering with it. None of my OF utilities were working and all threw the same error so I thought I had a messed up build. But eventually I found it was just a space in a folder name.
|
|
July 1, 2016, 11:00 |
|
#23 |
New Member
Vijaya Kumar. G
Join Date: Jun 2016
Location: Chennai, India & Aachen, Germany
Posts: 20
Rep Power: 10 |
As mentioned in the above threads, Directory and Mesh file names which are irregular (contains underscore, other symbols) are poisonous. I too was down with this problem. Changed all my file names and case directory names as simple Numbers and Characters
|
|
October 3, 2016, 12:13 |
|
#24 |
New Member
gned
Join Date: Oct 2012
Posts: 18
Rep Power: 14 |
dear mark,
I'm quite out of space in my ssd disk of my laptop by now. So I would often have the need to try/run/visualize some cases on an external USB I have, but which unfortunately is recognized as TOSHIBA EXT by the system, with a whitespace in the name! Is this possible modifying some files as fileName.H to make OF digest these names strings? |
|
October 6, 2016, 16:39 |
|
#25 | |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,981
Blog Entries: 45
Rep Power: 128 |
Quote:
Code:
mkdir -p $FOAM_RUN cd $FOAM_RUN ln -s "/media/username/TOSHIBA EXT" usbdisk
Using quotes for the path with spaces is necessary. The alternative would be to use the backslash: Code:
ln -s /media/username/TOSHIBA\ EXT usbdisk Code:
cd usbdisk Note: You don't need to delete the symbolic link when you safely eject the USB disk.
__________________
|
||
January 11, 2017, 17:08 |
|
#26 |
New Member
RK_Token
Join Date: Jan 2016
Location: Germany
Posts: 5
Rep Power: 10 |
Just in case, it may help someone.
I had the same problem but in my case I had a jupyter notebook file saved at the simulation case folder, with a space in its name "notebook name.ipynb". This was enough to break the reconstructPar command. |
|
January 11, 2017, 17:50 |
|
#27 |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,981
Blog Entries: 45
Rep Power: 128 |
Quick question @RK_Token: Which OpenFOAM version were/are you using?
I ask this because if it's one of the more recent versions, we can still have this fixed much sooner than later. And I am very glad that Python based Jupyter Notebooks are being used along with OpenFOAM! |
|
January 11, 2017, 18:13 |
|
#28 | |
New Member
RK_Token
Join Date: Jan 2016
Location: Germany
Posts: 5
Rep Power: 10 |
Hey @wyldckat I'm using OpenFOAM-4.1 64bit
Quote:
|
||
February 8, 2017, 07:26 |
|
#29 |
New Member
zhuyuehan
Join Date: Feb 2017
Posts: 2
Rep Power: 0 |
You may want to make a backup and copied some file then renamed it. and there is a space in the name of your execution file.
|
|
October 10, 2017, 07:18 |
|
#30 |
Member
Jingxue Wang
Join Date: Sep 2017
Posts: 58
Rep Power: 9 |
I also meet this problem just now.
I make a new folder and then copy all the inner files into this. And it worked. |
|
December 15, 2017, 03:49 |
|
#31 | |
Senior Member
Mark Olesen
Join Date: Mar 2009
Location: https://olesenm.github.io/
Posts: 1,714
Rep Power: 40 |
Quote:
FWIW this longstanding problem has now been fixed in the upcoming OpenFOAM-v1712 release. Now the POSIX readDir will silently (or noisily) drop file and directory names with weird characters that would cause OpenFOAM problems. |
||
December 25, 2018, 01:39 |
|
#32 |
New Member
|
Hello!
I faced a similar issue and solved it successfully. >> Create databases as time fileName::stripInvalid() called for invalid fileName 02vectorvelmag.png For debug level (= 2) > 1 this is considered fatal Aborted (core dumped) >> Solution>>>>> the file name "02vectorvelmag.png" is actually a .png file saved in my caseDirectory which is actually named as "02 vector vel mag.png" which I saved during post-processing of another case. So, I removed this file to another location and run the intended command once again. it worked. |
|
July 19, 2020, 16:32 |
|
#33 |
New Member
Siavash
Join Date: Jun 2020
Posts: 2
Rep Power: 0 |
||
January 11, 2021, 18:18 |
|
#34 | |
New Member
John Wooten, PhD
Join Date: Dec 2020
Location: Oak Ridge TN
Posts: 18
Rep Power: 5 |
Quote:
Perhaps it's something as simple as an extra file or directory in you setup folders. |
||
December 8, 2022, 22:27 |
|
#35 |
New Member
Join Date: Sep 2022
Posts: 19
Rep Power: 4 |
Maybe useful for someone. I met the similar error, i.e.
for time = 0LUID_inner fileName::stripInvalid() called for invalid fileName FLUID_inner For debug level (= 2) > 1 this is considered fatal when I run the case from Allrun script. But it run without this error if I input the same command in terminal. Finally I find there are two blank lines after the command which the above error emit. After delete these two blank lines, it runs successfully. I am new and not sure if you have already know this. |
|
Tags |
commandtouse, filename, reconstructpar, stripinvalid |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
reconstructParMesh not working with an axisymetric case | francesco | OpenFOAM Bugs | 4 | May 8, 2009 06:49 |