[7islands]

Hi,
Sorry for a silly question but is there any chance that you have an unintended whitespace between "source ~/OpenFOAM/OpenFOAM-1.3/.OpenFOAM-1.3" and "/bashrc" ...??

Anyway the message indicates that ~/OpenFOAM/OpenFOAM-1.3/.OpenFOAM-1.3/bashrc was not executed properly but no possible reason other than that comes to me.

Takuya

No there isn't but there is whitespace in my username if that makes a difference, i will clear everything and restart, maybe i did something wrong along the way and i don't realise it.
Thanks for the help
Liam

It was the whitespace in my windows user name and once i changed my home file in cygwin it worked.

However i now have a new problem i have set my ~/.bashrc so cygwin automatically loads ~/openfoam/openfoam-1.3/.openfoam-1.3/bashrc the message "FOAM install not found" showed up so i changed my ~/openfoam/openfoam-1.3/.openfoam-1.3/bashrc file to make it work but nothing i did worked. once i solved that problem a number of others popped up.

i was just wondering if i needed to change any of the names of my install directery "export WM_PROJECT_INST_DIR=$HOME/$WM_PROJECT" do i need to change "$home/" to "~/" or "home/liam/" or should it be working the way it is.

Thanks
Liam

[7islands]

Hi,
Generally you don't have to touch any of the shell scripts; they are supposed to work out-of-box if you followed the default installation procedure of cygwin. My one suspicion is that the HOME environment variable went inconsistent with your actual installation for some reason.

Takuya

[7islands]

Hi Cygwin users,
I am preparing for a new release of FoamX-cygwin shortly. This time the porting work won't be limited to FoamX. The next release will have the following features, aiming for wiping out all the undone porting works I ever know.

Is there anything else to do, which is supposed to be resolved in a short time? If anyone noticed remaining works, please let me know. As OF 1.4 also seems to be coming shortly, and I'm getting gradually busy, I'd like to make this the final release for OF 1.3.

Changes since FoamX-cygwin-20061212:
* New: paraFoam porting by way of the native OpenFOAM reader introduced in ParaView 2.6.
* New: patchTool porting.
* New: gmshToFoam now have compatibility with .msh files generated by Windows versions of Gmsh.
* New: foamDebugSwitches porting.
* Change: The version of JDK to which JAVA_HOME variable points is updated to jdk1.6.0.

Problems which will remain unresolved:
* Csh-alike shell support will be still incomplete.
* Installing FoamX-cygwin under a directory structure which contains whitespace in its pathnames will remain supported. Yes, I know that this is causing so many problems, and fixing it won't be technically so difficult, but requires too much testing work and time for me.

[7islands]

Hi Cygwin users,
This is the announcement of the third revision of FoamX-cygwin, FoamX-cygwin-20070224. Source and binary distributions are available. This time the porting work is not limited to FoamX itself. Most notable will be paraFoam porting by way of the native OpenFOAM reader introduced in ParaView 2.6. You can now launch paraFoam from both of command line and Foam Utilities -> postProcessing -> graphics -> paraFoam.

The URL:
http://oshima.eng.niigata-u.ac.jp/Op...-20070224.html

Changes since FoamX-cygwin-20061212:
* New: paraFoam porting by way of the native OpenFOAM reader introduced in ParaView 2.6. You need ParaView 2.6 (http://www.paraview.org/) to run paraFoam (Install it with default settings).
* New: patchTool porting. You need Java 3D (https://java3d.dev.java.net/) to run patchTool (Follow the installation instruction of Java 3D).
* New: gmshToFoam now have compatibility with .msh files generated by Windows versions of Gmsh.
* New: foamDebugSwitches porting.
* Change: The version of JDK to which JAVA_HOME variable points is updated to jdk1.6.0 from jdk1.5.0_10. If you'd like to use other versions, modify the JAVA_HOME line in $WM_PROJECT_DIR/.bashrc or .cshrc accordingly.

Known problems:
* Csh-alike shell support is still incomplete (just barely launches FoamX and paraFoam).
* Installing FoamX-cygwin under a directory structure which contains whitespace in its pathnames is not supported.

[marziolettich]

generally, paraFoam works very well with Cygwin, thanks to the excellent work of Takuya Oshima. But in a particular case I got this error message:


Generic Warning: In C:\dev\ParaView26\VTK\Rendering\vtkTkRenderWidget. cxx, line 626
A TkRenderWidget is being destroyed before it associated vtkRenderWindow is destroyed.This is very bad and usually due to the order in which objects are being destroyed.Always destroy the vtkRenderWindow before destroying the user interface components.


ERROR: In C:\dev\ParaView26\GUI\Widgets\vtkKWTkUtilities.cxx , line 221
vtkPVApplication (03DBCD30):
Script:
toplevel .1710 -class {ParaView} -visual best -highlightthickness 0
Returned Error on line 1:
this isn't a Tk applicationunable to create widget ".1710"
Stack trace:
this isn't a Tk applicationunable to create widget ".1710"
while executing
"toplevel .1710 -class {ParaView} -visual best -highlightthickness 0"



ErrorMessage
# Error or warning: There was a VTK Error in file: C:\dev\ParaView26\GUI\Widgets\vtkKWTkUtilities.cxx (221)
vtkPVApplication (03DBCD30):
Script:
toplevel .1710 -class {ParaView} -visual best -highlightthickness 0
Returned Error on line 1:
this isn't a Tk applicationunable to create widget ".1710"
Stack trace:
this isn't a Tk applicationunable to create widget ".1710"
while executing
"toplevel .1710 -class {ParaView} -visual best -highlightthickness 0"

This is quite strange, as it's a very simple 2d example and I don't know what could be that cause this crash. If someone experienced something similar, please post a reply here. Thanks!

[7islands]

Hi Marzio,
Actually I'm also having similar crashes especially when reading unstructured meshes even if they are
simple 2D ones (the tutorials/potentialFoam/cylinder case for example). My guess is that the ParaView OpenFoam reader code still has some works to be done, because ParaView also crashes even if such a case is read through the File menu of ParaView (not through the paraFoam script). I've been looking into the reader code when I have time but so far I have no success with it.

Terry Jordan, the writer of the nice reader code, might be able to propose some fix if you report the case in detail at the following "OpenFOAM reader in the ParaView CVS" thread:
http://www.cfd-online.com/OpenFOAM_D...es/1/3429.html

Takuya