Hi Adriana,
there is no particle-tracking implemented in GETM. However, you have to
compute the velocity fields, temperature, viscosity, ... and store these
fields with an high temporal resolution. Than you can use GITM, a
particle-tracking tool developed for GETM output fields. GITM is an
independent tool. Either you contact Johan van der Molen (CEFAS) or
Bianca Schippmann (IOW). They can help you to set up GITM.
>
> 2) Can I already make use of the vertical adaptive grid?
>
This is not a problem at all.
Cheers, ulf
> Thanks a lot!
> adriana
>
--
Ulf Gr�we
Leibniz Institute for Baltic Sea Research Warnemuende
Dept. for Physical Oceanography and Instrumentation
Seestrasse 15
D-18119 Rostock-Warnemuende
Germany
Pho. : +49 (381) 5197-358
Fax : +49 (381) 5197-440
Web : http://www.io-warnemuende.de/ulf-graewe-en.html
Room : 216
Ilja reported something similar and Karsten fixed the devel version.
Can you please try with the devel version and report back.
Probably we have to fix the stable then as well.
Regards,
Knut
> <mailto:gdjo...@math.uwaterloo.ca>
Karsten
PS: For the I don't know what time - please start a new thread when
raising a new issue.
You are using a 64 bit system - right?
Karsten
On Tue, Apr 17, 2012 at 11:56:42 -0400, Georges Djoumna wrote:
please excuse my question, but sometimes users are not familar with git
and I do not know your experience... :-)
Did you make a "git pull"? Do you see Karstens commit with "git log"?
Knut
>>> <mailto:gdjo...@math.uwaterloo.ca>
> Hi Knut,
> I am not familiar with git. I just use
> git clone git://getm.git.sourceforge.net/gitroot/getm/getm getm-git
>
> to download the code and then compiles it.
>
> I did not make a "git pull"
ok. please be aware that the default version you get after a clone is
the devel version. for the stable version you have to do (after the clone):
git checkout -b stable origin/stable
But this does not solve the problem... :-)
can you please try to compile the branch you get with:
git branch v2.2.0 origin/stable^1
git checkout v2.2.0
Regards,
Knut
thanks for your fast test and reply.
>
> By using
> git branch v2.2.0 origin/stable^1
> git checkout v2.2.0
>
> I successfully compile the code.
very interesting. Karsten and Ilja, can you sort that out?
>
> Should I use these command every time I want to compile the stable
> version v2.2.0?
This is only necessary if you clone again a new getm-git.
With the 1st command you created the branch v2.2.0 in you local
getm-git. With the 2nd command you switched to that branch. If you are
fine with continueing to work with that branch, you do not need to
execute any git commands.
Hope this helps,
Knut
Dear Georges,
thanks for your fast test and reply.very interesting. Karsten and Ilja, can you sort that out?
By using git branch v2.2.0 origin/stable^1
git checkout v2.2.0
I successfully compile the code.
git checkout master ?
On a 64 bit system I can do:
cd GETM/getm-git/
git checkout stable
git log - shows a message from Apr 18 10:01:27
cd ~/getm-setups/git/box_cartesian
make mpi - compiles OK - for testing I add a print statement to show the
size of 'sizeof_realtype' and I get 8.
So in short - the stable code works on 64 bit machines with update code.
Karsten
On Tue, Apr 17, 2012 at 11:56:42 -0400, Georges Djoumna wrote:
Dear GETM users,when compiling the stable version 2.2 of GETM with " export FABM=true", the following errors appear.
Ulf Gräwe
Leibniz Institute for Baltic Sea Research WarnemuendeDept. for Physical Oceanography and InstrumentationSeestrasse 15D-18119 Rostock-WarnemuendeGermanyTel. : +49 (381) 5197-358Fax : +49 (381) 5197-440