[jherb]

Dear OpenFOAMers,

I am not sure, why this was not reported here yet, but a new version of OpenFOAM was released last week (2014-02-10):

http://www.openfoam.org/version2.3.0/
https://github.com/OpenFOAM/OpenFOAM-2.3.x

Joachim

[wyldckat]

Hi Joachim,

Actually, the release notes are really misleading, because they only announced it yesterday: https://twitter.com/openfoam/statuse...44092042887168

As for the announcement here on the forum, it's stuck in moderation mode: http://www.cfd-online.com/Forums/ope...-v2-3-0-a.html - I don't have permissions to touch that section, so... we'll have to wait

Best regards,
Bruno

[jherb]

Unfortunately, the 2.3.0 breaks swak4Foam compilation (due to a new implementation of mesh interpolation).

[JR22]

Does anybody know if Helyx-OS 2.0.0 will work with OpenFoam 2.3?
Thanks.

[Dadou]

Hello Foamers,

I want to know if someone can help installing 2.3.x without deleting the 2.2.2 version already installed on my Ubuntu 12.04 LTS.


Thank you and sorry if there's already an answer.

Dadou

[wyldckat]

Greetings to all!

@Dadou: Here's some reading material: http://openfoamwiki.net/index.php/In...with_the_Shell - when you finish reading+studying that page, you should be able to install as many OpenFOAM versions and variants as you want

Best regards,
Bruno

[Dadou]

Originally Posted by wyldckat

Greetings to all!

@Dadou: Here's some reading material: http://openfoamwiki.net/index.php/In...with_the_Shell - when you finish reading+studying that page, you should be able to install as many OpenFOAM versions and variants as you want

Best regards,
Bruno

Greetings to you Bruno,

Thank you for the help

Kind Regards,

Dadou

[Dadou]

Originally Posted by wyldckat

Greetings to all!

@Dadou: Here's some reading material: http://openfoamwiki.net/index.php/In...with_the_Shell - when you finish reading+studying that page, you should be able to install as many OpenFOAM versions and variants as you want

Best regards,
Bruno

Hi Bruno,

I tried to follow and understand the content of the link you send me. now I have two versions of OpenFOAM, but when I open a terminal it's goes directly to the 2.3.0 version. I created two alias of222 for 2.2.2 version and of230 for the 2.3.0 but somehow doesn't read the first one.

Can you help me with this please?

Thank you


Dadou

[wyldckat]

Originally Posted by Dadou

now I have two versions of OpenFOAM, but when I open a terminal it's goes directly to the 2.3.0 version. I created two alias of222 for 2.2.2 version and of230 for the 2.3.0 but somehow doesn't read the first one.

Mmm... perhaps it's fixed if you follow the section I added yesterday: 2.2.1 Unable to change the shell environment until I log-out
It happened to me in openSUSE and Fedora (if I'm not mistaken) and only after logging out and logging back in, was the environment properly set-up.

[jherb]

swak4Foam was updated meanwhile (in the hg repository) and compiles well with OpenFOAM 2.3.0.

Originally Posted by jherb

Unfortunately, the 2.3.0 breaks swak4Foam compilation (due to a new implementation of mesh interpolation).

[Dadou]

It happened to me in openSUSE and Fedora (if I'm not mistaken) and only after logging out and logging back in, was the environment properly set-up.[/QUOTE]

I tried what you suggested but still have the same problem and try to follow the web site again but nothing. Do you have an idea about the why?

Hope you can help

thanks again

Regards

[wyldckat]

@Dadou: What is the content of the file indicated by this command?

echo $HOME/.bashrc

[Dadou]

Originally Posted by wyldckat

@Dadou: What is the content of the file indicated by this command?

echo $HOME/.bashrc

@Bruno,

After tipping the code you wrote, I got this :

/home/openfoam/.bashrc

[alexeym]

Hi,

I guess wyldckat meant 'cat $HOME/.bashrc'.

Actually even if you created aliases of222 and of230 but have a line 'source /path/to/openfoam/2.3.0/etc/bashrc' in your $HOME/.bashrc you'll get environment variables setup for OF 2.3.0 as soon as you open terminal.

[Dadou]

Originally Posted by alexeym

Hi,

I guess wyldckat meant 'cat $HOME/.bashrc'.

Actually even if you created aliases of222 and of230 but have a line 'source /path/to/openfoam/2.3.0/etc/bashrc' in your $HOME/.bashrc you'll get environment variables setup for OF 2.3.0 as soon as you open terminal.

Hi,

when I run the command you suggested, I have this in return :

openfoam@openfoam:~$ cat $HOME/.bashrc
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# If not running interactively, don't do anything
[ -z "$PS1" ] && return

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth

# append to the history file, don't overwrite it
shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar

# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then
    debian_chroot=$(cat /etc/debian_chroot)
fi

# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
    xterm-color) color_prompt=yes;;
esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then
    if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
        # We have color support; assume it's compliant with Ecma-48
        # (ISO/IEC-6429). (Lack of such support is extremely rare, and such
        # a case would tend to support setf rather than setaf.)
        color_prompt=yes
    else
        color_prompt=
    fi
fi

if [ "$color_prompt" = yes ]; then
    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\0                                   33[01;34m\]\w\[\033[00m\]\$ '
else
    PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
    PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
    ;;
*)
    ;;
esac

# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
    test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dirco                                   lors -b)"
    alias ls='ls --color=auto'
    #alias dir='dir --color=auto'
    #alias vdir='vdir --color=auto'

    alias grep='grep --color=auto'
    alias fgrep='fgrep --color=auto'
    alias egrep='egrep --color=auto'
fi

# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'

# Add an "alert" alias for long running commands.  Use like so:
#   sleep 10; alert
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo                                    error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'                                   ')"'

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.

if [ -f ~/.bash_aliases ]; then
    . ~/.bash_aliases
fi

# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if [ -f /etc/bash_completion ] && ! shopt -oq posix; then
    . /etc/bash_completion
fi

source /opt/openfoam222/etc/bashrc
source /opt/openfoam230/etc/bashrc

[alexeym]

Hi,

look at the two last lines of your .bashrc:

source /opt/openfoam222/etc/bashrc
source /opt/openfoam230/etc/bashrc

they are executed automatically when you start terminal. So by default you'll get environment of OpenFOAM 2.2.2.

You can do one of the following:
1. Comment out (or just remove) these lines and after you start terminal run one of your aliases (of222 or of230) depending on the version you'd like to use. I guess they are defined in $HOME/.bash_aliases?

2. Create a file .OpenFOAM-release with, put there version you'd like to use

echo '2.2.2' > $HOME/.OpenFOAM-release

and change those two last lines of your $HOME/.bashrc to

OF_VER=$(cat $HOME/.OpenFOAM-release)
if [ "$OF_VER" == "2.2.2" ]; then
  source /opt/openfoam222/etc/bashrc
fi
if [ "$OF_VER" == "2.3.0" ]; then
  source /opt/openfoam230/etc/bashrc
fi

and use that $HOME/.OpenFOAM-release to define version you'd like to use.

[Dadou]

Alexeym,

Thank you for the tips, I figured it out why it wasn't working. in the bash file we have set up the aliases and then it will be easy to "call" them.
Exemple :

alias of222='source /opt/openfoam222/etc/bashrc

Regards

[lramutti]

Hey guys,

I have been trying to work with the new version of OpenFOAM 2.3.0 and it seems that it does not even run successful cases that I have executed in OpenFOAM 2.2.1. It is frustrating. Do you guys have similar issues? Why is that?

Lucas

[wyldckat]

Greetings Lucas,

OpenFOAM is constantly evolving. It might be a bit troubling at first, but to me it seems to be for the best, really!

Whenever a new version comes out, take the time to read the release notes; for example, for OpenFOAM 2.3.0: http://www.openfoam.org/version2.3.0/ - there you'll find about most of the changes that have been made.

The detail then comes when you find a bug... which may or may not have already been fixed in the repository version: http://www.openfoam.org/download/git.php - which means that you might have to build from source code the latest version, in this case OpenFOAM 2.3.x, in order to be able to use OpenFOAM without said bug...

As for adapting your cases to the changes, check the changes made in the reference tutorials you've been following as reference.

Best regards,
Bruno

[lramutti]

Hey Bruno,

Thanks for the response and the link. It is quite interesting to see the modifications that were done in this new version. I know that it is possible to install ParaView 4.1.0 without installing OpenFOAM 2.3.0 however, I am not sure how. What I do know is that ParaView can be downloaded from their website as a binary RHEL 64 bit. However, the paraFoam utility will not work and the only way to access the case is by creating a .foam extension in the directory. By any chance do you know how to do this?

I will post the solution to my problem in case someone comes across it in the future:

leftSolid_to_heater 

    type            compressible::turbulentTemperatureCoupledBaffleMixed; 
    Tnbr            T; 
    kappa           solidThermo; 
    kappaName       none; 
    thicknessLayers (1e-3);           OPTIONAL
    kappaLayers     (5e-4);           OPTIONAL
    value           uniform 300;

Furthermore, I minor update is necessary in the fvSchemes script of the fluid as follows:

laplacian(rhorAUf, p_rgh) Gauss linear limited 0.333;

Please note that the Gauss linear limited 0.333 is subjected to changes depending on the scheme used to solve for the laplacian of the turbulent model.

Cheers

Lucas Mutti