Menu
▾
▴
Re: [Anuga-user] Anuga-user Digest, Vol 46, Issue 1 [SEC=UNCLASSIFIED]
|
From: <Gar...@ga...> - 2012-07-10 23:21:46
|
Hi Rajesh, Regarding the second part of your question (to do with the forcing terms)-- I don't think you should be having the forcing repeatedly defined in the loop. Cheers, Gareth. Gareth Davies Hydrodynamic Modeller | International Group Energy Division | GEOSCIENCE AUSTRALIA ____________________________________________________________ Phone: +61 2 6249 9655 Fax: +61 2 6249 9999 Email: Gar...@ga... Web: www.ga.gov.au Cnr Jerrabomberra Avenue and Hindmarsh Drive Symonston ACT GPO Box 378 Canberra ACT 2601 Australia Applying geoscience to Australia's most important challenges -----Original Message----- From: anu...@li... [mailto:anu...@li...] Sent: Tuesday, 10 July 2012 10:13 PM To: anu...@li... Subject: Anuga-user Digest, Vol 46, Issue 1 Send Anuga-user mailing list submissions to anu...@li... 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 anu...@li... You can reach the person managing the list at anu...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of Anuga-user digest..." Today's Topics: 1. regarding_tms_file (rajesh tailor) ---------------------------------------------------------------------- Message: 1 Date: Tue, 10 Jul 2012 16:19:09 +0530 From: rajesh tailor <tai...@gm...> Subject: [Anuga-user] regarding_tms_file To: anu...@li... Message-ID: <CAA1D9o6hMrSNL=XQx...@ma...> Content-Type: text/plain; charset="iso-8859-1" Hi All, I am using ANUGA for simulation of GLOF in hilly terrain. I tried to generate hydrograph (.tms file) using following code... from numpy import array, float from Scientific.IO.NetCDF import NetCDFFile from anuga.config import netcdf_float from anuga.abstract_2d_finite_volumes.util import file_function fid = open('hydrograph.txt') lines = fid.readlines() fid.close() time = [] q = [] for line in lines: fields = line.split(',') time.append( float(fields[0])) q.append( float(fields[1])) # Convert to NetCDF N = len(time) T = array(time, float) # Time (seconds) R = array(q, float) # Values (m3/s) # Create tms NetCDF file fid = NetCDFFile('hydrograph.tms', 'w') fid.institution = '1simulation' fid.description = '2simulation' fid.starttime = 0.0 fid.createDimension('number_of_timesteps', len(T)) fid.createVariable('time', netcdf_float, ('number_of_timesteps',)) fid.variables['time'][:] = T fid.createVariable('hydrograph', netcdf_float, ('number_of_timesteps',)) fid.variables['hydrograph'][:] = R fid.close() The input to the hydrograph.txt was discharge values with corresponding time, separated by comma... like following.. 0,20 300,200 600,500 and so on... But when I have used this in my simulation program before evolving through the domain... hydro = anuga.Inflow(domain, rate = file_function('hydrograph.tms', center = [4,4], radius = 10, verbose = False) domain.forcing_terms.append(hydro) It was giving error something like this... Traceback (most recent call last): File "NorthSikkimMeshGeneration_buff2.py", line 250, in <module> obj.mesh_gen_wid_sim() File "NorthSikkimMeshGeneration_buff2.py", line 144, in mesh_gen_wid_sim self.simulate() File "NorthSikkimMeshGeneration_buff2.py", line 231, in simulate hydro = anuga.Inflow(self.getDomain(), rate = file_function('hydrograph.tms', quantities = ['time','discharge']), center = [667940.19, 3102363.71], radius = 20, verbose = False) File "C:\Python25\lib\site-packages\anuga\abstract_2d_finite_volumes\file_function.py", line 138, in file_function args, kwargs) File "C:\Python25\lib\site-packages\anuga\abstract_2d_finite_volumes\file_function.py", line 212, in _file_function output_centroids=output_centroids) File "C:\Python25\lib\site-packages\anuga\abstract_2d_finite_volumes\file_function.py", line 291, in get_netcdf_file_function raise Exception, msg Exception: Quantities ['stage','xmomentum','ymomentum'] could not be found in file hydrograph.tms Can anybody tell me why it is giving this error.. Because in User manual of ANUGA it is written that tms file contains only temporal information only, not spatial information (related to time only) And one more question if I append something in forcing_terms, is there any need to pop it again in next iteration of evolve like following.. hydro = anuga.Inflow(domain, rate = 10, center = [5,5], radius = 10, verbose = False) domain.forcing_terms.append(hydro) for t in domain.evolve(yieldstep = ys, finaltime = ft): domain.forcing_terms.pop() hydro = anuga.Inflow(domain, rate = 20, center = [5,5], radius = 10, verbose = False) domain.forcing_terma.append(hydro) Is it correct or should i remove it before iterating for next discharge value.... There is a big difference in output result with poping the forcing_terms element for each iteration compared to without poping.... Thanks in advance, regards, Rajesh Tailor -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ------------------------------ _______________________________________________ Anuga-user mailing list Anu...@li... https://lists.sourceforge.net/lists/listinfo/anuga-user End of Anuga-user Digest, Vol 46, Issue 1 ***************************************** Geoscience Australia Disclaimer: This e-mail (and files transmitted with it) is intended only for the person or entity to which it is addressed. If you are not the intended recipient, then you have received this e-mail by mistake and any use, dissemination, forwarding, printing or copying of this e-mail and its file attachments is prohibited. The security of emails transmitted cannot be guaranteed; by forwarding or replying to this email, you acknowledge and accept these risks. ------------------------------------------------------------------------------------------------------------------------- |