Anuga-user Digest, Vol 42, Issue 2

9 views

Skip to first unread message

anuga-use...@lists.sourceforge.net

unread,

Feb 9, 2012, 6:43:12 AM2/9/12

to anuga...@lists.sourceforge.net

Send Anuga-user mailing list submissions to
anuga...@lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/anuga-user
or, via email, send a message with subject or body 'help' to
anuga-use...@lists.sourceforge.net

You can reach the person managing the list at
anuga-us...@lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Anuga-user digest..."

Today's Topics:

1. Recall: Anuga-user Digest, Vol 42, Issue 1 [SEC=UNCLASSIFIED]
(Leharne....@ga.gov.au)
2. Re: Anuga-user Digest, Vol 42, Issue 1 [SEC=UNCLASSIFIED]
(Leharne....@ga.gov.au)
3. Adding forcing terms to simulate incoming flow
(marcor...@libero.it)

----------------------------------------------------------------------

Message: 1
Date: Thu, 9 Feb 2012 09:25:35 +1100
From: <Leharne....@ga.gov.au>
Subject: [Anuga-user] Recall: Anuga-user Digest, Vol 42, Issue 1
[SEC=UNCLASSIFIED]
To: <marcor...@libero.it>
Cc: anuga...@lists.sourceforge.net
Message-ID:
<60D02F9C526B7F48B2194...@EXCCR01.agso.gov.au>
Content-Type: text/plain; charset="us-ascii"

Fountain Leharne would like to recall the message, "Anuga-user Digest, Vol 42, Issue 1 [SEC=UNCLASSIFIED]".

------------------------------

Message: 2
Date: Thu, 9 Feb 2012 09:24:57 +1100
From: <Leharne....@ga.gov.au>
Subject: Re: [Anuga-user] Anuga-user Digest, Vol 42, Issue 1
[SEC=UNCLASSIFIED]
To: <marcor...@libero.it>
Cc: anuga...@lists.sourceforge.net
Message-ID:
<60D02F9C526B7F48B2194...@EXCCR01.agso.gov.au>
Content-Type: text/plain; charset="us-ascii"

Hi Marco

ANUGA requires polygons to have unique vertices - as such you must not repeat the last point to close your polygon. So you need simply to delete either your first or last point and ANUGA automatically closes your polygon.

Let me know if this does not work.

Kind regards
Leharne Fountain

Leharne Fountain | Hazard and Risk Modeller

Risk Analysis Methods Section | Earth Monitoring and Hazards Group | Geoscience Australia

p +61 (0)2 6249 9078 | f +61 (0)2 6249 9929
e leharne....@ga.gov.au | www.ga.gov.au/hazards

Postal: GPO Box 378 Canberra ACT 2601 AUSTRALIA
Physical: Cnr Jerrabomberra Avenue & Hindmarsh Drive Symonston ACT 2609

When awaiting a reply, please note I work Monday, Tuesday, Thursday and Friday

-----Original Message-----
From: anuga-use...@lists.sourceforge.net [mailto:anuga-use...@lists.sourceforge.net]
Sent: Wednesday, 8 February 2012 02:45
To: anuga...@lists.sourceforge.net
Subject: Anuga-user Digest, Vol 42, Issue 1

Send Anuga-user mailing list submissions to
anuga...@lists.sourceforge.net

You can reach the person managing the list at
anuga-us...@lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Anuga-user digest..."

Today's Topics:

1. Example of Anuga implementation (Tom van Tilburg | Geodan)
2. csv formatting issue (marcor...@libero.it)
3. Re: csv formatting issue (marcor...@libero.it)
4. Re: csv formatting issue (Stephen Roberts)
5. Re: csv formatting issue (marcor...@libero.it)
6. Re: csv formatting issue (Stephen Roberts)

----------------------------------------------------------------------

Message: 1
Date: Wed, 11 Jan 2012 16:01:00 +0100
From: Tom van Tilburg | Geodan <tom.van...@geodan.nl>
Subject: [Anuga-user] Example of Anuga implementation
To: anuga...@lists.sourceforge.net
Message-ID: <4F0DA42C...@geodan.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi all,

For those interested, we just made a small post regarding the
implementation of ANUGA within a web-interface.

http://research.geodan.nl/?p=466

We used ANUGA as a demonstration model because of its quick deployment
capability and ease of use.

Regards,
Tom

--
--------------------------------------
Geodan
President Kennedylaan 1
1079 MB Amsterdam (NL)

T +31 (0)20 - 5711 350
E tom.van...@geodan.nl
www.geodan.nl | disclaimer
--------------------------------------

------------------------------

Message: 2
Date: Tue, 07 Feb 2012 14:54:17 +0100
From: "marcor...@libero.it" <marcor...@libero.it>
Subject: [Anuga-user] csv formatting issue
To: anuga...@lists.sourceforge.net
Message-ID: <4F312D09...@libero.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi All,

I'm an Anuga User since a few days only, and I'm trying to set up a
simple simulation, using real terrain data.
At the moment I'm concerned with file formats. I'm using Grass GIS to
export my simulation domain boundary as a polygon in csv format, but I
get a Python error concerning the way the csv file is formatted.
The extent file just contains the following lines (I have erased many
pieces of information Grass adds when exporting, but I used to get
errors even with the raw exported file):
686007.82 923006.11
686145.11 923006.11
686145.11 923145.11
686003.91 923145.6
686007.82 923006.11

and this is what I get on terminal:

File "/usr/lib/python2.6/dist-packages/anuga/geometry/polygon.py",
line 802, in read_polygon
polygon.append([float(fields[0]), float(fields[1])])
ValueError: invalid literal for float(): 686007.82 923006.11

I have no experience in Python Programming, but it clearly looks like an
issue connected with the way the csv file is formatted (maybe missing
headers, separators, ...).

Could anyone post the content of a .csv file containing the correct
information needed to describe a polygon?
Thanks in advance,
Marco

------------------------------

Message: 3
Date: Tue, 07 Feb 2012 16:15:02 +0100
From: "marcor...@libero.it" <marcor...@libero.it>
Subject: Re: [Anuga-user] csv formatting issue
To: Michael Simon <hydr...@web.de>, anuga...@lists.sourceforge.net
Message-ID: <4F313FF6...@libero.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi, thank you for your promptness.

I have tried to run the code varying some format characteristics; amongst them I tried to separate the values by commas, like the following:

686007.82,923006.11

686145.11,923006.11

686145.11,923145.11

686003.91,923145.60

686007.82,923006.11

But that just produced a slightly different error message:

File "/usr/lib/python2.6/dist-packages/anuga/geometry/polygon.py", line 802, in read_polygon

polygon.append([float(fields[0]), float(fields[1])])

ValueError: empty string for float()

The only .csv example I could find on the manual regards a gauge location (gauges.csv). I tried to follow those formatting guidelines, producing this:

easting,northing,elevation

686007.82,923006.11,0

686145.11,923006.11,0

686145.11,923145.11,0

686003.91,923145.60,0

686007.82,923006.11,0

but I still get errors:

File "/usr/lib/python2.6/dist-packages/anuga/geometry/polygon.py", line 802, in read_polygon

polygon.append([float(fields[0]), float(fields[1])])

ValueError: invalid literal for float(): easting

Thus I am still hanging on it. Any other advice?

Thank you so much, anyway!

Marco

On 02/07/2012 03:44 PM, Michael Simon wrote:
> Marco !!
>
> Very briefly without checking your case seriously. Sorry, but try this one.
>
> You need to create an ASCII-File with "Comma" delimiter.
>
> Does it help?
>
> Regards
>
> Mike
> -----Urspr?ngliche Nachricht-----
> Von: marcor...@libero.it [mailto:marcor...@libero.it]
> Gesendet: Dienstag, 7. Februar 2012 14:54
> An: anuga...@lists.sourceforge.net
> Betreff: [Anuga-user] csv formatting issue
>
> Hi All,
>
> I'm an Anuga User since a few days only, and I'm trying to set up a simple
> simulation, using real terrain data.
> At the moment I'm concerned with file formats. I'm using Grass GIS to export
> my simulation domain boundary as a polygon in csv format, but I get a Python
> error concerning the way the csv file is formatted.
> The extent file just contains the following lines (I have erased many pieces
> of information Grass adds when exporting, but I used to get errors even with
> the raw exported file):
> 686007.82 923006.11
> 686145.11 923006.11
> 686145.11 923145.11
> 686003.91 923145.6
> 686007.82 923006.11
>
> and this is what I get on terminal:
>
> File "/usr/lib/python2.6/dist-packages/anuga/geometry/polygon.py",
> line 802, in read_polygon
> polygon.append([float(fields[0]), float(fields[1])])
> ValueError: invalid literal for float(): 686007.82 923006.11
>
> I have no experience in Python Programming, but it clearly looks like an
> issue connected with the way the csv file is formatted (maybe missing
> headers, separators, ...).
>
> Could anyone post the content of a .csv file containing the correct
> information needed to describe a polygon?
> Thanks in advance,
> Marco
>
> ----------------------------------------------------------------------------
> --
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers is
> just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro
> Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Anuga-user mailing list
> Anuga...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/anuga-user
>
> .
>

------------------------------

Message: 4
Date: Wed, 08 Feb 2012 02:17:58 +1100
From: Stephen Roberts <stephen...@anu.edu.au>
Subject: Re: [Anuga-user] csv formatting issue
To: "marcor...@libero.it" <marcor...@libero.it>,
anuga...@lists.sourceforge.net
Message-ID: <4F3140A6...@anu.edu.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Maybe

686007.82,923006.11

686145.11,923006.11

686145.11,923145.11

686003.91,923145.60

causes an error because of the empty lines. Should be

686007.82,923006.11
686145.11,923006.11
686145.11,923145.11
686003.91,923145.60

Cheers
Steve

On 8/02/2012 2:15 AM, marcor...@libero.it wrote:
> Hi, thank you for your promptness.
>
> I have tried to run the code varying some format characteristics; amongst them I tried to separate the values by commas, like the following:
>
> 686007.82,923006.11
>
> 686145.11,923006.11
>
> 686145.11,923145.11
>
> 686003.91,923145.60
>
> 686007.82,923006.11
>
> But that just produced a slightly different error message:
>
> File "/usr/lib/python2.6/dist-packages/anuga/geometry/polygon.py", line 802, in read_polygon
>
> polygon.append([float(fields[0]), float(fields[1])])
>
> ValueError: empty string for float()
>
>
> The only .csv example I could find on the manual regards a gauge location (gauges.csv). I tried to follow those formatting guidelines, producing this:
>
> easting,northing,elevation
>
> 686007.82,923006.11,0
>
> 686145.11,923006.11,0
>
> 686145.11,923145.11,0
>
> 686003.91,923145.60,0
>
> 686007.82,923006.11,0
>
> but I still get errors:
>
> File "/usr/lib/python2.6/dist-packages/anuga/geometry/polygon.py", line 802, in read_polygon
>
> polygon.append([float(fields[0]), float(fields[1])])
>
> ValueError: invalid literal for float(): easting
>
> Thus I am still hanging on it. Any other advice?
>
> Thank you so much, anyway!
>
> Marco
>
>
>
>
>
>
> On 02/07/2012 03:44 PM, Michael Simon wrote:
>> Marco !!
>>
>> Very briefly without checking your case seriously. Sorry, but try this one.
>>
>> You need to create an ASCII-File with "Comma" delimiter.
>>
>> Does it help?
>>
>> Regards
>>
>> Mike
>> -----Urspr?ngliche Nachricht-----
>> Von: marcor...@libero.it [mailto:marcor...@libero.it]
>> Gesendet: Dienstag, 7. Februar 2012 14:54
>> An: anuga...@lists.sourceforge.net
>> Betreff: [Anuga-user] csv formatting issue
>>
>> Hi All,
>>
>> I'm an Anuga User since a few days only, and I'm trying to set up a simple
>> simulation, using real terrain data.
>> At the moment I'm concerned with file formats. I'm using Grass GIS to export
>> my simulation domain boundary as a polygon in csv format, but I get a Python
>> error concerning the way the csv file is formatted.
>> The extent file just contains the following lines (I have erased many pieces
>> of information Grass adds when exporting, but I used to get errors even with
>> the raw exported file):
>> 686007.82 923006.11
>> 686145.11 923006.11
>> 686145.11 923145.11
>> 686003.91 923145.6
>> 686007.82 923006.11
>>
>> and this is what I get on terminal:
>>
>> File "/usr/lib/python2.6/dist-packages/anuga/geometry/polygon.py",
>> line 802, in read_polygon
>> polygon.append([float(fields[0]), float(fields[1])])
>> ValueError: invalid literal for float(): 686007.82 923006.11
>>
>> I have no experience in Python Programming, but it clearly looks like an
>> issue connected with the way the csv file is formatted (maybe missing
>> headers, separators, ...).
>>
>> Could anyone post the content of a .csv file containing the correct
>> information needed to describe a polygon?
>> Thanks in advance,
>> Marco
>>
>> ----------------------------------------------------------------------------
>> --
>> Keep Your Developer Skills Current with LearnDevNow!
>> The most comprehensive online learning library for Microsoft developers is
>> just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro
>> Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-d2d
>> _______________________________________________
>> Anuga-user mailing list
>> Anuga...@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/anuga-user
>>
>> .
>>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Anuga-user mailing list
> Anuga...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/anuga-user

------------------------------

Message: 5
Date: Tue, 07 Feb 2012 16:30:54 +0100
From: "marcor...@libero.it" <marcor...@libero.it>
Subject: Re: [Anuga-user] csv formatting issue
To: Stephen Roberts <stephen...@anu.edu.au>
Cc: anuga...@lists.sourceforge.net
Message-ID: <4F3143AE...@libero.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi,
it worked this time!
Actually, it's kind of strange, because I had already tried to comma
separate the numbers, and the white lines you saw where just due to
email formatting.
However, apart from using commas, I also tried to cancel the last point,
as you suggested. That was automatically inserted by Grass GIS, which I
use to handle GIS data. This time the code produced no error related to
the .csv file.
In the end, this worked:
686007.82,923006.11
686145.11,923006.11
686145.11,923145.11
686003.91,923145.60

Thank you very much for your help!
I can now work to the following errors my code produced!
Marco

On 02/07/2012 04:17 PM, Stephen Roberts wrote:
> Maybe
>
> 686007.82,923006.11
>
> 686145.11,923006.11
>
> 686145.11,923145.11
>
> 686003.91,923145.60
>
> causes an error because of the empty lines. Should be
>
> 686007.82,923006.11
> 686145.11,923006.11
> 686145.11,923145.11
> 686003.91,923145.60
>
> Cheers
> Steve
>
> On 8/02/2012 2:15 AM, marcor...@libero.it wrote:
>> Hi, thank you for your promptness.
>>
>> I have tried to run the code varying some format characteristics;
>> amongst them I tried to separate the values by commas, like the
>> following:
>>
>> 686007.82,923006.11
>>
>> 686145.11,923006.11
>>
>> 686145.11,923145.11
>>
>> 686003.91,923145.60
>>
>> 686007.82,923006.11
>>
>> But that just produced a slightly different error message:
>>
>> File
>> "/usr/lib/python2.6/dist-packages/anuga/geometry/polygon.py", line
>> 802, in read_polygon
>>
>> polygon.append([float(fields[0]), float(fields[1])])
>>
>> ValueError: empty string for float()
>>
>>
>> The only .csv example I could find on the manual regards a gauge
>> location (gauges.csv). I tried to follow those formatting guidelines,
>> producing this:
>>
>> easting,northing,elevation
>>
>> 686007.82,923006.11,0
>>
>> 686145.11,923006.11,0
>>
>> 686145.11,923145.11,0
>>
>> 686003.91,923145.60,0
>>
>> 686007.82,923006.11,0
>>
>> but I still get errors:
>>
>> File
>> "/usr/lib/python2.6/dist-packages/anuga/geometry/polygon.py", line
>> 802, in read_polygon
>>
>> polygon.append([float(fields[0]), float(fields[1])])
>>
>> ValueError: invalid literal for float(): easting
>>
>> Thus I am still hanging on it. Any other advice?
>>
>> Thank you so much, anyway!
>>
>> Marco
>>
>>
>>
>>
>>
>>
>> On 02/07/2012 03:44 PM, Michael Simon wrote:
>>> Marco !!
>>>
>>> Very briefly without checking your case seriously. Sorry, but try
>>> this one.
>>>
>>> You need to create an ASCII-File with "Comma" delimiter.
>>>
>>> Does it help?
>>>
>>> Regards
>>>
>>> Mike
>>> -----Urspr?ngliche Nachricht-----
>>> Von: marcor...@libero.it [mailto:marcor...@libero.it]
>>> Gesendet: Dienstag, 7. Februar 2012 14:54
>>> An: anuga...@lists.sourceforge.net
>>> Betreff: [Anuga-user] csv formatting issue
>>>
>>> Hi All,
>>>
>>> I'm an Anuga User since a few days only, and I'm trying to set up a
>>> simple
>>> simulation, using real terrain data.
>>> At the moment I'm concerned with file formats. I'm using Grass GIS
>>> to export
>>> my simulation domain boundary as a polygon in csv format, but I get
>>> a Python
>>> error concerning the way the csv file is formatted.
>>> The extent file just contains the following lines (I have erased
>>> many pieces
>>> of information Grass adds when exporting, but I used to get errors
>>> even with
>>> the raw exported file):
>>> 686007.82 923006.11
>>> 686145.11 923006.11
>>> 686145.11 923145.11
>>> 686003.91 923145.6
>>> 686007.82 923006.11
>>>
>>> and this is what I get on terminal:
>>>
>>> File "/usr/lib/python2.6/dist-packages/anuga/geometry/polygon.py",
>>> line 802, in read_polygon
>>> polygon.append([float(fields[0]), float(fields[1])])
>>> ValueError: invalid literal for float(): 686007.82 923006.11
>>>
>>> I have no experience in Python Programming, but it clearly looks
>>> like an
>>> issue connected with the way the csv file is formatted (maybe missing
>>> headers, separators, ...).
>>>
>>> Could anyone post the content of a .csv file containing the correct
>>> information needed to describe a polygon?
>>> Thanks in advance,
>>> Marco
>>>
>>> ----------------------------------------------------------------------------
>>>
>>> --
>>> Keep Your Developer Skills Current with LearnDevNow!
>>> The most comprehensive online learning library for Microsoft
>>> developers is
>>> just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3,
>>> MVC3, Metro
>>> Style Apps, more. Free future releases when you subscribe now!
>>> http://p.sf.net/sfu/learndevnow-d2d
>>> _______________________________________________
>>> Anuga-user mailing list
>>> Anuga...@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/anuga-user
>>>
>>> .
>>>
>>
>> ------------------------------------------------------------------------------
>>
>> Keep Your Developer Skills Current with LearnDevNow!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-d2d
>> _______________________________________________
>> Anuga-user mailing list
>> Anuga...@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/anuga-user
>
>

------------------------------

Message: 6
Date: Wed, 08 Feb 2012 02:14:36 +1100
From: Stephen Roberts <stephen...@anu.edu.au>
Subject: Re: [Anuga-user] csv formatting issue
To: anuga...@lists.sourceforge.net, marcor...@libero.it
Message-ID: <4F313F...@anu.edu.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi Marco,

Probably just that the file should be comma separated, ie

686007.82, 923006.11
686145.11, 923006.11
686145.11, 923145.11
686003.91, 923145.6
686007.82, 923006.11

Also be careful with replicated points at start and end of the polygon.
The polygon as specified will probably work, but it is better to remove
the last point from the list.

So I would use

686007.82, 923006.11
686145.11, 923006.11
686145.11, 923145.11
686003.91, 923145.6

Cheers
Steve

On 8/02/2012 12:54 AM, marcor...@libero.it wrote:
> Hi All,
>
> I'm an Anuga User since a few days only, and I'm trying to set up a
> simple simulation, using real terrain data.
> At the moment I'm concerned with file formats. I'm using Grass GIS to
> export my simulation domain boundary as a polygon in csv format, but I
> get a Python error concerning the way the csv file is formatted.
> The extent file just contains the following lines (I have erased many
> pieces of information Grass adds when exporting, but I used to get
> errors even with the raw exported file):
> 686007.82 923006.11
> 686145.11 923006.11
> 686145.11 923145.11
> 686003.91 923145.6
> 686007.82 923006.11
>
> and this is what I get on terminal:
>
> File "/usr/lib/python2.6/dist-packages/anuga/geometry/polygon.py",
> line 802, in read_polygon
> polygon.append([float(fields[0]), float(fields[1])])
> ValueError: invalid literal for float(): 686007.82 923006.11
>
> I have no experience in Python Programming, but it clearly looks like an
> issue connected with the way the csv file is formatted (maybe missing
> headers, separators, ...).
>
> Could anyone post the content of a .csv file containing the correct
> information needed to describe a polygon?
> Thanks in advance,
> Marco
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Anuga-user mailing list
> Anuga...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/anuga-user

------------------------------

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d

------------------------------

_______________________________________________
Anuga-user mailing list
Anuga...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/anuga-user

End of Anuga-user Digest, Vol 42, Issue 1
*****************************************

------------------------------

Message: 3
Date: Thu, 09 Feb 2012 12:43:01 +0100
From: "marcor...@libero.it" <marcor...@libero.it>
Subject: [Anuga-user] Adding forcing terms to simulate incoming flow
To: anuga...@lists.sourceforge.net
Message-ID: <4F33B145...@libero.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi all,

I need to simulate a flooding scenario, due to river levee breach. I
have a discharge hydrograph (flow in m3/s) and I want to use it within
my simulation.
First of all, I thought the best way to input my hydrograph would have
been to use a forcing term, precisely the Inflow class, but I would like
to have some feedback on this: are there better ways to input localized
hydrographs, when modeling phenomena like a levee breach?

Secondly, it looks like I can't properly define the hydrograph time
serie according to the required NetCDF tms format. I tried to format my
data in a hydrograph.tms file as follows:

t, flow
0.0, 0.00
0.1, 0.10
0.2, 0.30
0.3, 0.75
0.4, 0.99
0.5, 1.20
0.6, 1.70
0.7, 1.70
0.8, 1.70
0.9, 1.70
1.0, 1.70

and then I called as follow:

hydrograph = Inflow(center=(686010, 923100), radius=2,
rate=file_function('hydrograph.tms', quantities='flow'))
domain.forcing_terms.append(hydrograph)

this causes the following error message:

'Must be a NetCDF File'

Thanks in advance!
Marco

------------------------------

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/

------------------------------

_______________________________________________
Anuga-user mailing list
Anuga...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/anuga-user

End of Anuga-user Digest, Vol 42, Issue 2
*****************************************

Reply all

Reply to author

Forward

0 new messages