RE: Loads Corresponding to sources in Hydrodynamics model - Forum - Delft3D Flexible Mesh
Forum
- Home
- 3. Archive
- 3.5 DELWAQ
- RE: Loads Corresponding to sources in Hydrodynamics model
RE: Loads Corresponding to sources in Hydrodynamics model
Abdulla Mohamed, modified 9 Years ago.
Loads Corresponding to sources in Hydrodynamics model
Youngling Posts: 6 Join Date: 5/24/16 Recent Posts
Hello,
I am trying to setup a water quality model in Delta Shell using D-Water Quality.
To test things out, I built a small D-FLOW FM model in DeltaShell and had a source discharge going into to the bottom layer of the model (Atleast I think this is what the model is doing, based on if I defined the source boundary correctly).
In trying to set up the D-Water Quality model, in Delta Shell, I am trying to assign a discharge load in the D-Water Quality model where the source is coming in.
To do this I have defined a decaying tracer via the ".sub" file.
In the earlier version of the WAQ I was able to define a ".tim" for the time series load concentrations of this decaying tracer, simulating a CSO discharge coming into the model with the flow at the given time interval.
I think the way to define this sort of time vaying pollution loads have changed with the new D-Water Quality in Delta Shell.
I was reading section 4.10.3 in the D-Water Quality users Manual and it was not very clear how this file should be formatted.
Below is a quote from the manual:
"The WAQ GUI does not automatically create pollution loads to represent these sources. Instead,
we suggest that the user imports them as pollution loads, imports a dataset with the
flow data (see Section on Boundary Conditions and Loads Data) and adds one or more
datasets with the concentration data. If the same data are used which are used to define
the sources in the hydrodynamics model, there should not be any problem."
Does this means I have to have two time series files, one with the flow data and one with the loads data? I thought D-Water Quality will already have all f the flows/discharges data from the ".hyd" file generated from the D-FLOW FM.
Also I am wondering how the format of this file should look like. ( seems like it has to be a .CSV file from the manual, but exact formatting is unclear)
Any help with this will be very much appreciated.
Thanks very much
Abdulla
I am trying to setup a water quality model in Delta Shell using D-Water Quality.
To test things out, I built a small D-FLOW FM model in DeltaShell and had a source discharge going into to the bottom layer of the model (Atleast I think this is what the model is doing, based on if I defined the source boundary correctly).
In trying to set up the D-Water Quality model, in Delta Shell, I am trying to assign a discharge load in the D-Water Quality model where the source is coming in.
To do this I have defined a decaying tracer via the ".sub" file.
In the earlier version of the WAQ I was able to define a ".tim" for the time series load concentrations of this decaying tracer, simulating a CSO discharge coming into the model with the flow at the given time interval.
I think the way to define this sort of time vaying pollution loads have changed with the new D-Water Quality in Delta Shell.
I was reading section 4.10.3 in the D-Water Quality users Manual and it was not very clear how this file should be formatted.
Below is a quote from the manual:
"The WAQ GUI does not automatically create pollution loads to represent these sources. Instead,
we suggest that the user imports them as pollution loads, imports a dataset with the
flow data (see Section on Boundary Conditions and Loads Data) and adds one or more
datasets with the concentration data. If the same data are used which are used to define
the sources in the hydrodynamics model, there should not be any problem."
Does this means I have to have two time series files, one with the flow data and one with the loads data? I thought D-Water Quality will already have all f the flows/discharges data from the ".hyd" file generated from the D-FLOW FM.
Also I am wondering how the format of this file should look like. ( seems like it has to be a .CSV file from the manual, but exact formatting is unclear)
Any help with this will be very much appreciated.
Thanks very much
Abdulla
Arjen Markus, modified 7 Years ago.
RE: Loads Corresponding to sources in Hydrodynamics model
Youngling Post: 1 Join Date: 1/26/11 Recent Posts
The previous version of the user-interface indeed was able to import the ".src" files that contain the flow rates as specified in the hydrodynamic calculation. Unfortunately this is not (yet) possible in DeltaShell. (Note, however, it has become practice to use open boundaries to model such discharges.) In this particular case you do have a discharge not connected to the (land) boundary and then you have to prepare a CSV file with the right information.
These CSV files have a simple format:
- The first line contains the names of the columns, separated by commas
- All following lines contain the date/time and the values
Here is a simple example:
timeBlock,location,substance,value
2014-01-01 00:00:00,WWTP,FLOW,0.10
2014-02-01 00:00:00,WWTP,FLOW,0.10
2014-01-01 00:00:00,WWTP,Ecoli,1.0E12
2014-02-01 00:00:00,WWTP,Ecoli,1.0E12
The first column, timeBlock, is the date and time for the observations/data points. Besides timeBlock you can also specify timeLinear - indicating either block functions or piecewise linear functions.
The second column is the name of the location, as you can use one file for several such waste loads.
The third column is the name of the quantity (substance is a bit of a misnomer of course, but that is ignored by the GUI). You specify one value for one substance at one location on each line.
The fourth column is the actual value of that substance for that time at that location.
These CSV files work for boundary conditions too and for timeseries for process parameters. In these cases of course "FLOW" is not a special substance.
These CSV files have a simple format:
- The first line contains the names of the columns, separated by commas
- All following lines contain the date/time and the values
Here is a simple example:
timeBlock,location,substance,value
2014-01-01 00:00:00,WWTP,FLOW,0.10
2014-02-01 00:00:00,WWTP,FLOW,0.10
2014-01-01 00:00:00,WWTP,Ecoli,1.0E12
2014-02-01 00:00:00,WWTP,Ecoli,1.0E12
The first column, timeBlock, is the date and time for the observations/data points. Besides timeBlock you can also specify timeLinear - indicating either block functions or piecewise linear functions.
The second column is the name of the location, as you can use one file for several such waste loads.
The third column is the name of the quantity (substance is a bit of a misnomer of course, but that is ignored by the GUI). You specify one value for one substance at one location on each line.
The fourth column is the actual value of that substance for that time at that location.
These CSV files work for boundary conditions too and for timeseries for process parameters. In these cases of course "FLOW" is not a special substance.