CrisB

Members
  • Content count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral

About CrisB

  • Rank
    Member
  1. Rusty, Great news. Please pass on my thanks to whoever developed the PTM gage coverage; this is very useful. Cheers
  2. As far as I know for ADCIRC you have to create your wind file in the appropriate format outside of SMS (e.g. by rearranging your data inside excel), and then you specify which format this is in the model control->wind tab. The specifications of the formats for input wind files is given in the ADCIRC user manual, and can be found at: http://www.adcirc.org/documentv48/Input_file_descriptions.html
  3. Ben, I've not tried running PTM with CMS inputs, but instead converted CMS-flow data to a mesh and ran the PTM using this, which worked fine. This may be worth trying...
  4. I've converted wind files in netcdf to ASCII text format for ADCIRC forcing using Matlab (the free 'octave' which is very similar may also be capable of doing this). You can also convert using the 'ncdump' command that is packaged with netcdf. For GRIB files you can use the 'wgrib' utility to convert to text. If you are lucky your data will be in the much more friendly GRIB v2, which you can use 'wgrib2' with. Rusty I would recommend looking at incorporating functionality to read netcdf into SMS: this is a standard file format used by meteorological agencies around the world to store atmospheric data, which can be used to drive the models that SMS supports (e.g. ADCIRC).
  5. Bret, One more thing: if you're looking for an unstructured grid model that does sediment transport you could get in touch with the TuFlow Finite Volume model developers (http://www.tuflow.com/TUFLOW%20FV/TUFLOW_FV_Description.html).
  6. Bret, I've asked aquaveo before about this but got no reply. I asked Jason Fleming (ADCIRC guru: http://seahorsecoastal.com/) and here was his reply: The version of ADCIRC that you have does not provide sediment transport capability. One reason for this is that the numerical algorithms that it employs do not guarantee local (i.e., element level) mass conservation. Thats not to say that it doesn't conserve mass locally; its just that it is not theoretically guaranteed to do so. Normally, when we want to look at the motion of conserved quantities in an ADCIRC velocity field, we seed the flow with passive particles and apply a particle tracking algorithm as a post processing step. The visualizations that were posted by the ADCIRC development group (http://www.nd.edu/~adcirc/sed.htm) were produced by a research version of the code that solves a different set of equations. These equations do guarantee element-level mass conservation and are therefore perfectly suited to sediment transport modeling. This research version is referred to as "the DG version of ADCIRC" because these equations are called Discontinuous Galerkin (as opposed to Continuous Galerkin in the current version of ADCIRC). So as I understand it, the version of ADCIRC bundled with SMS does not do sediment transport.
  7. Vince, As I understand it, STWAVE calculates wave radiation stress that can then be used as input into a flow model (e.g. cms-flow). It is this stress acting on the flow model's hydrodynamics that leads to the simulation of wave setup by the flow model. I don't think SMS 10.1 supports coupling of STWAVE and CMS-Flow however, only CMS-flow with CMS-Wave, through the steering module. You can have 2-way coupling whereby the CMS-wave radiation stress drives currents in CMS-Flow, which then supplies its water level and currents to CMS-wave to calculate their effect on the waves. I read in the CMS-Wave manual that it can calculate an approximation to wave setup by itself (i.e. without coupling to cms-flow), though I haven't explored this option. Cris
  8. Does anyone know how to calculate stream function using the SMS data calculator? I've got a PTM output which I think would be interesting to compare against the stream function from my mesh's velocity field. Would an automatic calculation be a useful addition to the data calculator?
  9. Thanks, this works. Interestingly this bug only occurs for a CMS-Flow grid to scatter point, not CMS-Wave grid to scatter point. I have sent a sample project indicating this to technical support.
  10. SMS 10.1.8 and 'save as type jpeg'. I've used screen capture to get around this problem but this is not a solution when I want to create animations using film loop (the same problem occurs). Can you recreate this problem?
  11. When converting vector data from a cartesian grid to scatter point, it seems that any angle that the grid axes is from 0 is not taken into account in the conversion. Hence, the scatterpoint vectors are in error by that same angle. Is this a bug?
  12. I've noticed that when you use this method, any background images loaded in are not saved in the image file. For example when adding a georeferenced tif file to a project and trying to save as jpeg, the image from the tif file is absent.
  13. Thanks
  14. In a recent talk on SMS at a CIRP workshop in New Orleans in May, a slide (32 - Spatial Data Coverages) suggests you can make a rose plot in SMS: http://cirp.usace.army.mil/presentations/workshops/MVN10/pdfs/10-Thursday_SMS_Overview.pdf How do you do this? I have SMS 10.1.8 and can't see this option in the 'plot wizard' box.
  15. Can I also suggest adding the 'Background' and 'Border' features that are available in the 'Create Text Object' function in the Annotations module? It is difficult to see the legend sometimes and these features would help a lot.