Jump to content
GMS, SMS, and WMS User Forum

Chris Blount

Members
  • Content Count

    50
  • Joined

  • Last visited

  • Days Won

    1

Chris Blount last won the day on August 3 2009

Chris Blount had the most liked content!

Community Reputation

4 Neutral

About Chris Blount

  • Rank
    Senior Member

Contact Methods

  • Website URL
    http://blogs.gtsav.gatech.edu/chrisblount
  • ICQ
    0

Profile Information

  • Location
    Savannah, GA
  1. Chris Blount

    Minor bug in 10.1

    I think I found a minor but annoying bug in SMS 10.1 with the 2D mesh polygon properties. I'm wanting to interpolate a different dataset onto part of my grid so I created a polygon to isolate the area of interest and used the existing nodes mesh option. I've done this plenty of times in the past. I recently used the Truncate Values option in the Interpolation dialog box and it worked fine. However, every time I tried a reinteroplation after that the values were truncated with the previously specified values even without the box being checked. I even tried changing the truncation values to be well outside the values of my dataset so it wouldn't affect the calculations, but the original truncation values were still used. I was able to solve this by changing the coverage type to something other than ADCIRC and then changing back to ADCIRC. That seemed to clear everything out so could reset the options. Everything works now, but I thought I would give everyone a heads up. Chris
  2. Chris Blount

    SMS colorbars

    Is there a way to change the orientation of contour colorbars to horizontal? If not, I'd suggest this for the next release with more options for the labels as well (ie., show only every other or third label, etc.). Being able to export objects in an EPS format as well would be helpful for creating better figures in other software like Adobe Illustrator. Thanks, Chris
  3. Hi Chris, you haven't answer to me yet about solve adcirc wind problem. If you can overcome adcirc problem, we plan paying to you 200 $ within our project budget. I'm looking forward for your respond as soon as possible. Regards,

    mestan

  4. Chris Blount

    Insert new mesh in existing mesh

    Chris, I've had a similar problem when I tried merging meshes. However, try going to Nodes -> Options and check "Retriangulate voids when deleting" if it isn't already. Please let me know if merging with this option on works. I haven't tried it yet, but I was going to try it myself when I needed to merge meshes again. Chris
  5. The fort.22 is the generic wind input file and the format depends on the NWS setting in the control file (fort.15). See the fort.22 page on the ADCIRC site for descriptions. You'll have to process the netCDF files to match the format you pick. Chris
  6. Hi Chris, I couldn't fix the problem at fort.19 file TAU error. I'm in Istanbul Technical University Civil Eng.Dep. This is very important for my project. Can you send your mail adress to me and help me if I send my sms files to you? My mail adress is mestanclef@yahoo.com Regards, mestan

  7. Chris Blount

    ADCIRC Error

    For the fort.19 error, it means you have an elevation specified boundary in your grid (fort.14) but since you don't have the boundary forcing specified in the fort.15 (NTIF and NBRF) it's looking for the fort.19 with non-periodic forcing data. If you're wanting to use tides, then use the tidal forcing tab in the model control to set up the boundary forcing. Otherwise, you'll need to supply a fort.19 file. I'm not sure if you can set the fort.19 up in SMS or you have to do it yourself because I've never used it. The second part about tau0 is not a fatal error, but it is important for accuracy. From the ADCIRC webpage: "TAU0 = Generalized Wave-Continuity Equation (GWCE) weighting factor that weights the relative contribution of the primitive and wave portions of the GWCE. If "primitive_weighting_in_continuity_equation" is specified as a nodal attribute in the fort.15 file above, this line will be read in but ignored. If a nodal attribute file is not used or "primitive_weighting_in_continuity_equation" is in the nodal attribute (fort.13) file, but not specified in the fort.15 file this TAU0 parameter will be used. = 0, the GWCE is a pure wave equation. > 1, the GWCE behaves like a pure primitive continuity equation. A good rule of thumb for setting TAU0 is to set it equal to the largest value of an equivalent linear friction factor (e.g, for linear friction TAU0 = TAU; for quadratic friction TAU0 = maximum (speed*CF/depth). Typical values for TAU0 are in the range of 0.001 - 0.01. = -1, the TAU0 is spatially varying but constant in time; it is calculated according to depth as follows: If the depth is >=10 TAU0 is set to 0.005, if the depth is < 10, TAU0 is set to 0.020. = -2, the TAU0 is spatially varying but constant in time; it is calculated according to depth as follows: if the depth is >=200 TAU0 is set to 0.005, if the depth is < 200 but > 1, then TAU0 is set to 1/depth, and if depth < 1, TAU0 is set to 1.0. = -3, the TAU0 varies spatially. In high resolution areas, it also varies in time, and is dependent on the local friction and a tau0 "base" value (set by the user in the fort.13 file). High resolution areas are designated by a user by setting the tau0 in those areas to a value greater than 0.025 then Tau0 is calculated by Tau0 = Tau0base+1.5*Tk. The ceiling for the resulting tau0 in the calculation is 0.2. If Tau0base < 0.25 then Tau0 = Tau0base. = -5, the TAU0 varies spatially and in time, and is dependent on the local friction; it is limited to a range specified by Tau0FullDomainMin and Tau0FullDomainMax. If the above values have 0.1 added to them (i.e., resulting in 3.1, 5.1, etc), then the tau0 is also written out to a fort.tau0 file in the same format and with the same timing as the fort.63 file. The purpose of this file is simply to allow the user to verify that the tau0 values are being calculated and set as intended." I've been using tau0=-5, but you also have to manually add another line with Tau0FullDomainMin and Tau0FullDomainMax (see the fort.15 page). Chris
  8. Chris Blount

    ADCIRC Error

    I didn't notice anything wrong other than a zero WTIMINC. This is the time interval between wind inputs and has to be greater than zero. Chris
  9. Chris Blount

    ADCIRC Error

    I'm not in the loop in terms of development, but I have noticed a few slight changes between v47 and v48 in the input format. This may not have been fixed in the preproscessing done by SMS. Can you post your fort.15? Chris
  10. Chris Blount

    ADCIRC Error

    It means that something isn't formatted right in the fort.15. Did you manually change anything in the fort.15 after SMS produced it? What version are you using (should say in the fort.16 output header)? Chris
  11. Chris Blount

    WIND ADCIRC

    It might help to know the intent of the model. If you want to force the entire model with a single wind speed then NWS=3 or 5 might work. You'll have to preprocess the data to the appropriate format and name the file "fort.22" for use by ADCIRC. The ADCIRC homepage has an example for NWS=3 (APES test case) that might be useful to look at. Chris
  12. Chris Blount

    Steady-state run on ADCIRC

    Abhishek, Setting NOLICAT to zero turns off the time-derivative terms, but I don't think this is what you'd want. I'm not sure exactly what you're referring to without knowing the reference, but I'm guessing you might want to look at the harmonic analysis features of ADCIRC. From this, you can get the steady component of water surface elevation (fort.53) and velocity (fort.54). I hope this helps. Chris
  13. Chris Blount

    SMS 10.1 ADCIRC Model Control file

    I don't know about the SMS problems, but the ADCIRC error is due to a change is how than changed the input for submergence state is given from v45 to v46. In v45 a fort.12 was used to specify the submergence state and now a fort.13 file contains input nodal attributes (variable friction, the submergence state, etc.). See the ADCIRC documentation. Version 48 isn't up there yet, but I don't think anything has changed between 47 and 48 with regards to the nodal attributes. Chris
  14. Chris Blount

    ADCIRC fort.63 dataset

    Aha! Consider this my bonehead question of the week. I didn't know you could edit the file name during the import! It just never occurred to me to try it there. Thanks, Chris
  15. Chris Blount

    ADCIRC fort.63 dataset

    Rusty, Is there a way to rename mesh datasets in 10.1? For example, when I import a maxele.63 file or multiple fort.63 files from different runs with ADCIRC the default name is "Water Surface Elevation (63)". I used to be able to change this in 10.0 by right clicking on the name. I can still do this with scatter datsets. Also, I've never been able to get the mesh datasets' new names to be saved for later sessions. For each new session I had to reload the files and rename them to keep track of everything. Both of these functions would be extremely useful especially since the new SWAN+ADCIRC program outputs files in unit 63 (H, T, and rad. stress) and 64 (direction) formats and they all end up with the default names when opened in SMS. Thanks, Chris
×