Greetings,
There have been some recent questions about running HE5 under the Lahey Fortran
95 Express version 7 compiler on computers with 64 bit Vista.
LF95 version 7.1 (shipped with recent orders for HE5) will NOT install correctly
under 64 bit Vista.
LF95 version 7.2, which Lahey is now shipping, does (according to Lahey) install
and run under 64 bit Vista, but it runs as 32 bit. So if you upgrade to LF95
7.2, you can at least run HE5 on 64 bit Vista machines, but you are NOT getting
64 bit accuracy. Lahey says they have no plans to develop a 64 bit version of
LF95 for Vista 64. They do support 64 bits on the Linux version of LF95
Express.
If you really want 64 bits, you need to go to Linux or use a different compiler
that runs on Vista 64. Either of those options would require you to modify the
basic HE5 code. I have not tried either approach since I do not have a Vista 64
or a Linux machine.
Regards,
Curt
Greetings HE5 users,
I have just posted a file, Updates.zip, to the files section of the Users' Group
website. This file contains various "revison 1" updates to the original HE5
code.
To update your HE5.0 code to Revision 1 (HE5.0.1):
1) download the file Updates.zip from the Users' Group website
2) put the Updates.zip file in the HE5 root directory, and unzip to get a
directory HE5/Updates
3) run installRev1.bat in the Updates folder
This revision fixes a bug in the Lroot output, fixes issues loading the excel
output, updates the DPF phase function data files so that all file names match
in EL and HL versions, and adds support to non-US regional settings.
Future updates will add to this Updates directory, so don't delete it after this
first update. Future user support will assume that you have upgraded your HE5
code to revision 1, so please install this update.
Let us know if you have questions.
Regards,
Curt Mobley (curtis.mobley@...)
Lydia Sundman (LSundman@...)
The Lahey LF95 v7.1 compiler (what I've been shipping with HydroLight)
does not install correctly on 64 bit Vista. Lahey said in January that
they are working on a fix for 64 bit Vista, however their website today
doesn't say anything about the current v7.2 being able to run on 64 bit
windows machines, just Win32. The Lahey LF64 v8.1 compiler for 64 bit
Linux does run OK as far as I know, but that doesn't answer your
question about MS Windows machines. I doubt that anyone has tried HE5
on Windows 7 beta.
Curt
erehm wrote:
>
>
> Is anyone running Hydrolight/Ecolight Ver. 5 on a 64-bit operating
> system, e.g., MS Vista-64 or Windows 7 64 bit Beta?
>
>
--
-----------------------------------
Curtis D. Mobley, Ph.D.
Vice President and Senior Scientist
Sequoia Scientific, Inc.
2700 Richards Road, Suite 107
Bellevue, WA 98005
voice: 425-641-0944 ext 109
fax: 425-643-0595
email: curtis.mobley@...
WWW: www.sequoiasci.com
personal: www.curtismobley.com
-----------------------------------
I had run the previous version of Hydrolight on a serial computer with
about 800 processors. We had the challenge of performing thousands of
short simulations (each taking about a minute to execute). There was no
parralelization, though.
We simply compiled the HL code to run it under Linux. We did not modify
the code. Every simulation was being separately assigned to a different
processor. There was a homemade batch queuing software that was taking
care of an optimal assignment of executions to different processors.
servet
erehm wrote:
>
>
> Has anyone parallelized Hydrolight and/or Ecolight to run on either
> multicore processors on a single machine (requiring rework of code to
> be reentrant) or on multiple machines (e.g., via MPI)?
>
> Let's assume for the moment that we're not including any inelastic
> scattering, so that one could compute all requested wavelengths in
> parallel...
>
> .
> Web Bug from
>
http://geo.yahoo.com/serv?s=97359714/grpId=14196913/grpspId=1705083247/msgId=66/\
stime=1243584225/nc1=1/nc2=2/nc3=3
>
>
Has anyone parallelized Hydrolight and/or Ecolight to run on either multicore
processors on a single machine (requiring rework of code to be reentrant) or on
multiple machines (e.g., via MPI)?
Let's assume for the moment that we're not including any inelastic scattering,
so that one could compute all requested wavelengths in parallel...
Raghu,
The way H works is that IOPs like a and b must be in SI units of
1/meters. Normally chl is in mg Chl/m^3 and chl-specific spectra a* or
b* are in m^2/mg. Thus
a (1/m) = chl (mg/m^3) x a* (m2/mg)
Normally you read in a file with chl(depth) (if the concentration varies
with depth) and a*(wavelength) to get a(depth,wavelength). See page 46
of the HE5 Tech Doc for the file formats.
If you have chl in ppb/l then you would need to define a* in units of
liter/(ppb m) so that a = chl x a* has units of 1/m. I think I'd
convert ppb/l to mg/m^3 (= microgram/liter) and stick with the standard
way people measure chl, so as not to confuse things.
Likewise, CDOM is usually specified as the absorption at 440 nm (read
from a file, if not constant with depth), with the wavelength dependence
of a_CDOM at other wavelengths given by an exponential function, which
can be specified in the UI. See Tech Doc eq 7.
Curt
Raghavendra S. Mupparthy wrote:
>
>
> Hello All!
>
> I am newbie to HE5. I have hyperspectral radiometer data with chl
> profiles and CDOM concentration profiles in ppb/l. Now how can I
> specify CDOM's a() & b(), which the Case2 model seem to need as input?
> Do I need to estimate a & b from cdom concentration profile?
>
> Cheers
> Raghu
>
>
--
-----------------------------------
Curtis D. Mobley, Ph.D.
Vice President and Senior Scientist
Sequoia Scientific, Inc.
2700 Richards Road, Suite 107
Bellevue, WA 98005
voice: 425-641-0944 ext 109
fax: 425-643-0595
email: curtis.mobley@...
WWW: www.sequoiasci.com
personal: www.curtismobley.com
-----------------------------------
Hello All!
I am newbie to HE5. I have hyperspectral radiometer data with chl profiles and
CDOM concentration profiles in ppb/l. Now how can I specify CDOM's a() & b(),
which the Case2 model seem to need as input?
Do I need to estimate a & b from cdom concentration profile?
Cheers
Raghu
Finally, at long last, HydroLight-EcoLight version 5.0 (HE5) is now
shipping!
All licensed version 4 users will receive HE5 as a free upgrade. To
receive your upgrade, please provide me with the following information
(send to curtis.mobley@...):
1) The name of the person and institution who originally licensed
version 4. [I may not know who this in cases where the code is being
run by a student or programmer I don't know.]
2) The serial number of the Lahey Fortran 95 compiler that came with
your copy of Hydrolight. [To get this, open a command window (e.g.,
use start-->programs-->accessories-->command prompt) and type LF95 at
the prompt. Lahey will come back with a block of information; the
first line contains the Lahey release number and the serial number.]
3) The full postal mailing address where I should send HE5. Include a
phone number for express mail shipments.
The newly posted file WhatsNewinHE5.pdf gives an overview of the new
features of HE5.
Cheers,
Curt
No, if you just replace the 4 lines with the new lines it should work. Note that this fix has been included in HE5 (which will be released shortly).
I will e-mail you a new qasky.f file with the fix directly.
Regards,
Lydia
On Aug 13, 2008, at 12:17 PM, caffe1nefree wrote:
Any one having a problem trying to fix this?
I keep on getting 'rsunz' is used but never set in line 388.
Same with 'rsuna'.
--- InHydroLightUsers@yahoogroups.com, "Curtis Mobley" <curtis.mobley@...> wrote: > > Hello HydroLight users, > > Marcos Montes and Joe Rhea of the U.S. Naval Research Lab recently > noted that the solar azimuthal angle computed by HydroLight when you > enter the date, time, and location is incorrect. This does NOT affect > HydroLight's computations, since only the zenith angle (which is > correct) is used to determine the sky radiance. (Indeed, the sun's > azimuthal angle is set to zero by H after it is computed within the > RADTRAN subroutine "sunang".) However, the incorrect azimuthal angle > is in the printout and therefore should be correct, even if it is not > used in computations. > > To correct this bug: > > 1) go to file qasky.f in the maincode directory > 2) go to subroutine sunang in that file > 3) replace (or comment out) these four lines of code: > > sintmp = sin(abs(rha))*cos(rsdec)/sin(rsunz) > rsuna = asin(sintmp) > if(ylat .gt. sdec) rsuna = 180.0 / rad - rsuna > if(xha .gt. 0.) rsuna = 360.0/rad - rsuna > > with these three lines of code: > > sna=cos(rsdec)*sin(rha) > csa=sin(rlat)*cos(rha)*cos(rsdec)-sin(rsdec)*cos(rlat) > rsuna=(atan2(sna,csa)+4.0*atan(1.0)) > > The computed sun azimuth angle will then be correct. > > As a test case, if you use (in the H GUI) > day=164 > GMT=12.0 > longitude=-80.100 > latitude=26.020 > > the printout should show > sun zenith angle = 71.57 deg > sun azimuth angle = 72.60 deg > > (The old, incorrect azimuth was 107.40 deg.) > > Many thanks to Joe and Marcos for finding this bug and for giving me > code that works. This is what I had in mind when I set up this users' > forum. > > Cheers, > > Curt >
Any one having a problem trying to fix this?
I keep on getting 'rsunz' is used but never set in line 388.
Same with 'rsuna'.
--- In HydroLightUsers@yahoogroups.com, "Curtis Mobley"
<curtis.mobley@...> wrote:
>
> Hello HydroLight users,
>
> Marcos Montes and Joe Rhea of the U.S. Naval Research Lab recently
> noted that the solar azimuthal angle computed by HydroLight when you
> enter the date, time, and location is incorrect. This does NOT affect
> HydroLight's computations, since only the zenith angle (which is
> correct) is used to determine the sky radiance. (Indeed, the sun's
> azimuthal angle is set to zero by H after it is computed within the
> RADTRAN subroutine "sunang".) However, the incorrect azimuthal angle
> is in the printout and therefore should be correct, even if it is not
> used in computations.
>
> To correct this bug:
>
> 1) go to file qasky.f in the maincode directory
> 2) go to subroutine sunang in that file
> 3) replace (or comment out) these four lines of code:
>
> sintmp = sin(abs(rha))*cos(rsdec)/sin(rsunz)
> rsuna = asin(sintmp)
> if(ylat .gt. sdec) rsuna = 180.0 / rad - rsuna
> if(xha .gt. 0.) rsuna = 360.0/rad - rsuna
>
> with these three lines of code:
>
> sna=cos(rsdec)*sin(rha)
> csa=sin(rlat)*cos(rha)*cos(rsdec)-sin(rsdec)*cos(rlat)
> rsuna=(atan2(sna,csa)+4.0*atan(1.0))
>
> The computed sun azimuth angle will then be correct.
>
> As a test case, if you use (in the H GUI)
> day=164
> GMT=12.0
> longitude=-80.100
> latitude=26.020
>
> the printout should show
> sun zenith angle = 71.57 deg
> sun azimuth angle = 72.60 deg
>
> (The old, incorrect azimuth was 107.40 deg.)
>
> Many thanks to Joe and Marcos for finding this bug and for giving me
> code that works. This is what I had in mind when I set up this users'
> forum.
>
> Cheers,
>
> Curt
>
Hi Curt,
I appreciate any help you can give my student, Mimi Szeto, who is
using Hydrolight for her master's thesis work and for a presentation
at Ocean Optics this fall.
Will you be going to ocean optics?
I hope you are well and that I'll see you in Tuscany!
Best wishes,
Janet
At 01:24 PM 8/12/2008, you wrote:
>I don't know what problem you're referring to. Rrs can certainly be
>smaller than 2x10^-3. I can't answer a question like this without the
>inputs and outputs from your run, so I can understand what problem you
>are having.
>
>Curt
>
>caffe1nefree wrote:
> >
> > Hi,
> >
> > Has anyone experienced the problem where modeled Hydrolight Rrs can be
> > no lower than 2x10^-3 ??
> >
> >
>
>--
>-----------------------------------
>Curtis D. Mobley, Ph.D.
>Vice President and Senior Scientist
>Sequoia Scientific, Inc.
>2700 Richards Road, Suite 107
>Bellevue, WA 98005
>voice: 425-641-0944 ext 109
>fax: 425-643-0595
>email: curtis.mobley@...
>WWW: www.sequoiasci.com
>personal: www.curtismobley.com
>-----------------------------------
>
>
>
>------------------------------------
>
>Yahoo! Groups Links
>
>
>
I don't know what problem you're referring to. Rrs can certainly be
smaller than 2x10^-3. I can't answer a question like this without the
inputs and outputs from your run, so I can understand what problem you
are having.
Curt
caffe1nefree wrote:
>
> Hi,
>
> Has anyone experienced the problem where modeled Hydrolight Rrs can be
> no lower than 2x10^-3 ??
>
>
--
-----------------------------------
Curtis D. Mobley, Ph.D.
Vice President and Senior Scientist
Sequoia Scientific, Inc.
2700 Richards Road, Suite 107
Bellevue, WA 98005
voice: 425-641-0944 ext 109
fax: 425-643-0595
email: curtis.mobley@...
WWW: www.sequoiasci.com
personal: www.curtismobley.com
-----------------------------------
I have just posted HydroLight Technical Note #6 (file
HTN6_infdeep_sources.pdf). This note discusses the sometimes puzzling
behavior of the light field near the lower boundary of the water
column in runs that use an infinitely deep water column and also
include inelastic effects (fluorescence or Raman scatter) or
bioluminescence. A work-around for H version 4 is given. This
work-around will be automated in version 5.
Dr. Minsu Kim has created an Ocean Optics Phytoplankton Simulator
(OOPS) that lets you build up IOPs for different types of
phytoplankton, including effects of particle size distributions, index
of refraction, and other parameters. There is an option for doing
HydroLight simulations with the IOPs you construct.
Minsu now has a website devoted to OOPS at www.kimsoops.net
I haven't yet played with the latest OOPS version myself, but I invite
you to take a look at the OOPS website and contact Minsu at
kimsoops@... if you would like to download his software package.
Cheers,
Curt Mobley
Hi Curt,
Can you tell me more about ecolight? (point me to a website?)
J.
At 01:52 PM 2/18/2008, you wrote:
>Guillaume,
>
>Using H to create an extensive LUT would indeed be prohibitive in
>computer time. What you need is the EcoLight code, with will be a part
>of version 5. Ecolight runs *much* faster than H. (the LUT used in my
>2005 Applied Optics paper was created with an early version of
>EcoLight). My goal is to ship v5 within a month. We're doing the last
>testing now, and writing the new user's guide and such.
>
>Curt Mobley
>
>dribreg wrote:
> >
> > Hi everybody,
> >
> > I would like to test a LUT approach but the computer time requirement
> > is huge if I want to cover the full extent of our local IOP, R bottom
> > , depth and bb/b variability. I have already put a lot of constraints
> > on the depth vs R and b vs a but it still would take 1 year on my
> > computer. So I wonder if anybody has created an extensive LUT from
> > Hydrolight which is accessible ?
> >
> > I have found on the web that a routine (hydroPPT) was created in order
> > to prepare batch run for hydrolight. Has this routine been distributed ?
> >
> > thank you
> > Guillaume
> >
> >
>
>--
>-----------------------------------
>Curtis D. Mobley, Ph.D.
>Vice President and Senior Scientist
>Sequoia Scientific, Inc.
>2700 Richards Road, Suite 107
>Bellevue, WA 98005
>voice: 425-641-0944 ext 109
>fax: 425-643-0595
>email: curtis.mobley@...
>WWW: www.sequoiasci.com
>personal: www.curtismobley.com
>-----------------------------------
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
Janet W. Campbell
Associate Dean for Research
College of Engineering and Physical Sciences
Kingsbury Hall, Room W255
University of New Hampshire
Durham, NH 03824
tele: 603-862-2022
fax: 603-862-2486
email: janet.campbell@...
Guillaume,
Using H to create an extensive LUT would indeed be prohibitive in
computer time. What you need is the EcoLight code, with will be a part
of version 5. Ecolight runs *much* faster than H. (the LUT used in my
2005 Applied Optics paper was created with an early version of
EcoLight). My goal is to ship v5 within a month. We're doing the last
testing now, and writing the new user's guide and such.
Curt Mobley
dribreg wrote:
>
> Hi everybody,
>
> I would like to test a LUT approach but the computer time requirement
> is huge if I want to cover the full extent of our local IOP, R bottom
> , depth and bb/b variability. I have already put a lot of constraints
> on the depth vs R and b vs a but it still would take 1 year on my
> computer. So I wonder if anybody has created an extensive LUT from
> Hydrolight which is accessible ?
>
> I have found on the web that a routine (hydroPPT) was created in order
> to prepare batch run for hydrolight. Has this routine been distributed ?
>
> thank you
> Guillaume
>
>
--
-----------------------------------
Curtis D. Mobley, Ph.D.
Vice President and Senior Scientist
Sequoia Scientific, Inc.
2700 Richards Road, Suite 107
Bellevue, WA 98005
voice: 425-641-0944 ext 109
fax: 425-643-0595
email: curtis.mobley@...
WWW: www.sequoiasci.com
personal: www.curtismobley.com
-----------------------------------
Hi everybody,
I would like to test a LUT approach but the computer time requirement
is huge if I want to cover the full extent of our local IOP, R bottom
, depth and bb/b variability. I have already put a lot of constraints
on the depth vs R and b vs a but it still would take 1 year on my
computer. So I wonder if anybody has created an extensive LUT from
Hydrolight which is accessible ?
I have found on the web that a routine (hydroPPT) was created in order
to prepare batch run for hydrolight. Has this routine been distributed ?
thank you
Guillaume
Dear HydroLight users,
Two sharp-eyed users just found a bug in the subroutine that reads in
depth profiles of CDOM absorption at a given wavelength (values of
CDOM absorption were being set to zero at all depths). Either no one
has ever used this option before, or no one has actually looked
closely at their output and noticed the error until now.
I have placed a new file, cdomdata.f, on the Users' Group under the
files section. You should download this file and place it in the
HydroLight "maincode" directory and overwrite the current file with
the same name. The new routine will fix the bug in either version 4.2
or 4.3.
Many thanks to Zhongping Lee and Keping Du for finding this bug.
Cheers,
Curt Mobley
Jing,
H version 5, which is now almost ready for release, runs down to 300
nm. As for help with your specific problem (since I don't know exactly
what you've done to extend your copy of version 4), contact Lydia
Sundman at Lsundman@.... We can send you our extended
version of the RADTRAN sky code as used in H5, which might help cure
your irradiance problem between 300 and 350.
Curt
cindyzju wrote:
> hi, everybody
>
> I am trying to extend the hydrolight simulation up to 300nm. Here
> is what I did. I extended gcirrad.txt file to 300 nm as well as input
> data for all the water components. During the calculation it
> shows "astar error" up to 350nm on the terminal. Water IOP are
> calculated properly but irradiance is not calculated correctly from 300
> to 350 nm. Do we need to change anything else in the input file or in
> the program so that it can perform the simulation up to 300nm properly?
>
> thanks
> Jing
>
>
--
-----------------------------------
Curtis D. Mobley, Ph.D.
Vice President and Senior Scientist
Sequoia Scientific, Inc.
2700 Richards Road, Suite 107
Bellevue, WA 98005
voice: 425-641-0944 ext 109
fax: 425-643-0595
email: curtis.mobley@...
WWW: www.sequoiasci.com
personal: www.curtismobley.com
-----------------------------------
hi, everybody
I am trying to extend the hydrolight simulation up to 300nm. Here
is what I did. I extended gcirrad.txt file to 300 nm as well as input
data for all the water components. During the calculation it
shows "astar error" up to 350nm on the terminal. Water IOP are
calculated properly but irradiance is not calculated correctly from 300
to 350 nm. Do we need to change anything else in the input file or in
the program so that it can perform the simulation up to 300nm properly?
thanks
Jing
In H4.2, all of the required user input for a run is provided by incfiles.for and iroot.txt. As long as you can provide those two files, and handle compiling, you should be able to make a Hydrolight run on a non-Windows platform. Note that in H4.1 and other earlier releases of Hydrolight, the file gcirrad.txt was also read (for atmospheric parameters).
Looking forward, in version 5 of Hydrolight, all input is specified in the iroot.txt file itself (incfiles.for is replaced by a static routine with IF tests), and the EXE only needs to be recompiled when a user-supplied routine is called. This should make life easier for those writing their own input-generating codes or calling Hydrolight recursively.
Regards,
Lydia Sundman
On Oct 18, 2007, at 11:14 AM, helbigja wrote:
As I understand the Hydrolight, the GUI creates incfiles.for which contains a number of appropriate subroutine calls. This file is then used in compiling an executable. The GUI also writes Iroot.txt which contains many parameters and file names which are read at execution time.
Therefore, if one wants to construct an ensemble of simulations that differ in their input parameter values, one could create incfiles in Windows, transfer it to Linux and compile there. In addition, one could also write a program (e.g. in MATLAB or FORTRAN) to generate a series of Iroot's and simulations (Of course, one could do this in Windows as well, but some of us have reasons for wanting to work in Linux).
This would seem to be any easy way to use Hydrolight in Linux without going to the trouble of writting a program to generate incfiles.
As I understand the Hydrolight, the GUI creates incfiles.for which
contains a number of appropriate subroutine calls. This file is then
used in compiling an executable. The GUI also writes Iroot.txt which
contains many parameters and file names which are read at execution
time.
Therefore, if one wants to construct an ensemble of simulations that
differ in their input parameter values, one could create incfiles in
Windows, transfer it to Linux and compile there. In addition, one
could also write a program (e.g. in MATLAB or FORTRAN) to generate a
series of Iroot's and simulations (Of course, one could do this in
Windows as well, but some of us have reasons for wanting to work in
Linux).
This would seem to be any easy way to use Hydrolight in Linux without
going to the trouble of writting a program to generate incfiles.
Is my logic or understanding flawed?
Many Thanks for comments,
Jim Helbig
Hi Elena,
As I wrote in my message, I did not pursue the challenge of running the
GUI through Wine because I did not really need it. However I am pretty
sure you can get some help from the community that develop and maintain
Wine. They are very active and helpful.
I am sorry but I am overworked right now, I have no time to look at it.
Please let us know if you resolve the issue
good luck
--- In HydroLightUsers@yahoogroups.com, "Elena Torrecilla"
<torrecillautm@...> wrote:
>
> Hi Zhiqiang and Servet,
>
> I have installed HL in a FAT32 partition and used the HL executable
> and the GUI through Wine. I had to install the MSVBVM60.dll and
> COMDLG32.OCX to succeed.
>
> The problem I have is when the HL complilation is taking place via GUI
> I get an error message that says that the simulation .FOR file is not
> found. I try to search that file and I realize that it already exists.
>
> I don't know why HL is not able to find it...? Have you resolved that?
>
> Thanks and regards,
>
> Elena
>
> --- In HydroLightUsers@yahoogroups.com, Servet Ahmet Cizmeli
> <sa.cizmeli@> wrote:
> >
> > Hi Zhiqiang,
> >
> > Just in case you might want to run the HL DOS executable in Linux
> > through wine, I figured out that you don't need to create a FAT32
> > partition. Now there is an EXT3 (Linux) partition driver for Windows :
> > http://ext2fsd.sourceforge.net/
> >
> > With this tool, you can mount and read/write Linux EXT2 and EXT3
> > partitions from Windows. After installing ext2fsd in Windows, you
only
> > have to install HL in windows into your EXT3 Linux partition and
voila!
> > You can switch to Linux and use the HL executable (and the GUI)
through
> > Wine or run your own executable you compiled for Linux.
> >
> > a minor detail but just in case...
> > best
> > Servet
> >
>
Hi Zhiqiang and Servet,
I have installed HL in a FAT32 partition and used the HL executable
and the GUI through Wine. I had to install the MSVBVM60.dll and
COMDLG32.OCX to succeed.
The problem I have is when the HL complilation is taking place via GUI
I get an error message that says that the simulation .FOR file is not
found. I try to search that file and I realize that it already exists.
I don't know why HL is not able to find it...? Have you resolved that?
Thanks and regards,
Elena
--- In HydroLightUsers@yahoogroups.com, Servet Ahmet Cizmeli
<sa.cizmeli@...> wrote:
>
> Hi Zhiqiang,
>
> Just in case you might want to run the HL DOS executable in Linux
> through wine, I figured out that you don't need to create a FAT32
> partition. Now there is an EXT3 (Linux) partition driver for Windows :
> http://ext2fsd.sourceforge.net/
>
> With this tool, you can mount and read/write Linux EXT2 and EXT3
> partitions from Windows. After installing ext2fsd in Windows, you only
> have to install HL in windows into your EXT3 Linux partition and voila!
> You can switch to Linux and use the HL executable (and the GUI) through
> Wine or run your own executable you compiled for Linux.
>
> a minor detail but just in case...
> best
> Servet
>
Hi Zhiqiang,
Just in case you might want to run the HL DOS executable in Linux
through wine, I figured out that you don't need to create a FAT32
partition. Now there is an EXT3 (Linux) partition driver for Windows :
http://ext2fsd.sourceforge.net/
With this tool, you can mount and read/write Linux EXT2 and EXT3
partitions from Windows. After installing ext2fsd in Windows, you only
have to install HL in windows into your EXT3 Linux partition and voila!
You can switch to Linux and use the HL executable (and the GUI) through
Wine or run your own executable you compiled for Linux.
a minor detail but just in case...
best
Servet
Hello Zhiqiang,
Are you sure you don't want to run HL through "wine" in Linux and avoid
compiling? It's very easy. First install "wine".
Then using the GUI, in windows, create your HL run (let's name it ac9_013).
Then, in Linux, open a shell prompt and type :
cd /h42/maincode
wine maincode.exe < ../run/batch/Iac9_013.txt
If you don't have the new Linux drivers that allow read/write to a
windows NTFS partition, you might have to install HL on a FAT32
partition so that Linux can write to it.
***************************************************************************
If you really want to compile the code, here is how I did...
As I told you, I used Intel Fortran compiler under Linux, which is a
commercial software. You might want to try out other compilers. I'd be
interested in knowing the results.
*in IOshorten.f90, comment out all the windows module declarations
and calls to the function GetShortPathName
*In IOshorten.f90 (near line 47), modify the open statement
IF(lreturn.gt.0) then
open(iounit, file=shortfn, status='old', ACTION='read')
to read
IF(1) then
open(iounit, file=longfn, status='old', ACTION='read')
* Rename the file Dimens.inc to DIMENS.INC
* Remove the last lines of
SLAcom.f
BLAS.f
* Modify Initial.f line 693 for
write(10,fmt="(//' ERROR:',/' depths are not monotonically incre
1asing, or are too close together (deltazK =',f6.4,')',)") deltazK
to read
write(10,fmt="(//' ERROR:',/' depths are not monotonically incre
1asing, or are too close together (deltazK =',f6.4,')')") deltazK
* Modify irradat.f line 13 for
INCLUDE 'dimens.inc'
to read
INCLUDE 'DIMENS.INC'
* Modify setdflts.f around lines 64-68
comment lines 64-65 to read
c sl='\ '
c sysl=sl(1:1)
and comment-out lines 67-68 to read
bsl='/ '
sysl=bsl(1:1)
*IN gcirrad.f, main.f and setdflts.f:
replace all occurrences of
character*24 gcifile
to
character*30 gcifile
*Run the GUI to create a specific HL run (for example, let's name this
run ac9_St_013). The GUI will create the file batch/ac9_St_013.for
* To compile hydrolight:
cd maincode
ifort -c *.f
(this will create all the object files)
ifort batch/ac9_St_013.for *.o -I. -o hdrl_exec_ac9
(this will compile the hdrl_exec_ac9.for file that was created by the
GUI for your specific HL run and link it into the executable file called
hdrl_exec_ac9 ).
To run HL, type in the shell prompt:
hdrl_exec_ac9 < ../run/batch/Iac9_St_013.txt
Hope it works
good luck
servet
Zhiqiang Chen wrote:
> Hi Servet:
>
> Thank you very much for your message. It is exactly my purpose to avoid
> GUI to run HL because i am trying to run quite a lot simulations.
>
> Could you please fill me up more information about how to compile those
> code? I am having HL version 4.2 and using Linux FC4 OS. I am not
> familar with compilation of codes, thus you are really appreciated if
> you can provide information as detailed as possible.
> such as
> what compiler??
> what switch should be turn on?
> is a makefile available?
>
> thanks;
>
> zhiqiang
>
> */Servet Ahmet Cizmeli <sa.cizmeli@...>/* wrote:
>
> Hi Zhiquang
>
> You can always compile the source code under Linux. I succeeded under
> Linux with the (commercial) Intel fortran compiler. But this means that
> you won't have access to the graphical user interface (GUI) and you'll
> have to modifiy the input files and run the program by hand. In
> order to
> compile, you might have to modify a couple of fortran files but the
> modifications are minor. Let me know if you are willing to take the
> challenge.
>
> I also tried to run the GUI under Linux through "wine" (a software for
> Linux to run windows programs). I nearly succeeded (went through
> many of
> the input windows) but had an error at the end. I did not follow it up
> because I did not have time at that moment but I feel that the GUI can
> be made functional with "wine".
>
> Whether or not you succeed to run the GUI in "wine", if you are under
> Linux, you can always easily run the DOS executable maincode.exe under
> "wine". I am sure it would work like a charm.
>
> good luck
> servet
>
> Zhiqiang Chen wrote:
> >
> >
> > Hi all:
> >
> > Can I ask a question about HL?
> >
> > I read a message talking about a Linux version of HL? Has someone
> > suceeded in this effort? If so, how can I get a copy of it?
> >
> > thanks;
> >
> > zhiqiang
> >
>