| Message/Author |
|
|
 Tri (Tri) posted on Monday, July 02, 2007 - 04:18 pm
|
|
|
Dear All,
I have run CAESAR to test if I can get acceptable water surfaces from an anastomosing river system, and I can have.The results are ok.
Now, I would like to explore more features of CAESAR and I would be very happy if any of you could answer my questions.
At the Files tab
+ The "default" DEM data file is whole9.dat. However, I have used a file *.txt and it worked very well, I wonder if there is any difference between *.dat and *.txt.
+ How about others input files (i.e. Grain data file, Bedrock data file, Rainfall data file, and Variable M file)? If they have the extension of *.dat or *.txt?
+ I have tried to create a "Variable M file" with the same structure of DEM data file (e.g. M.txt). It means each pixcel has different M values. The created file also had a coordination system. In other words, it is the same what we can see from DEM data file. However, when I pressed "load data", there is error says that the model may not run properly. I do not know what wrong? probably my "Variable M file" is not in correct format (i.e. *.dat or *.txt) or not in correct structure???
+ if you could send me an example of each needed file (i.e. Grain data file, Bedrock data file, Rainfall data file, Variable M value file), it must be very helpful.
Many thanks for your help.
Best regards,
Tri PD }Van |
|
|
| Tri (Tri) posted on Tuesday, July 03, 2007 - 01:54 pm
|
|
|
Dear All,
I have answers for my question about the structure of the input files.
1. Grain data file
The structure is:
<x> <y> (coordinate) <grain>
e.g.
1 1 0.02
1 2 0.05
2. Bed rock data - to allocate where the rock exists in the DEM
The structure is:
<x> <y> (coordinate)
e.g.
5 7
5 8
5 9
3. Rainflall data - to distribute the hourly rainfall to the area
The structure is ONE column of rainfall in (mm)
e.g.
0.005
0.005
0.00
0.00
4. Variable M file
The structure is ONE column of M value
e.g.
0.020
0.010
0.005
0.018
However, I have not known for sure what M is. Is it Manning's n? and if it is organised in column like this, which value is allocated for which site? (because Manning's is spatially different, isn't it?)
Best regards,
Tri PD Van
pdtv@soton.ac.uk |
|
|
|
|
Hi Tri,
Bedrock data is in the same format as the DEM - it is a DEM of the bedrock elevations.
M is a value in the hydrological model (used in catchment mode). I controls the rate of increase and decrease of the hydrograph. It is from TOPMODEL and there is quite alot of literature describing its values.
Tom |
|
|
|
|
Dear Prof.,
I have created grain.txt file as I wrote in the discussion part of the webpage of CAESAR (http://www.coulthard.org.uk/discus/messages/3/61.html?1183533042)
It works quite well if the details look like this, for example:
1 38 0.065
1 39 0.065
2 41 0.065
2 45 0.065
3 48 0.064
3 43 0.064
4 44 0.064
4 47 0.064
5 38 0.065
7 42 0.065
However, if I added more value (e.g. number of columns and rows) like this, for example:
100 382 0.065
110 391 0.065
2 41 0.065
2 45 0.065
I received the error.
So, I wonder what is the meaning of the frist two numbers in each row. Are they x and y coordination as I wrote in the disscussion part?
I am looking forward to hearing from you.
Best regards,
--
Tri P.D. Van |
|
|
|
|
| 131 3 9848 0 0.0287999999832238 0.00439999999743697 0.00379999999778647 0.00579999999662147 0.0135999999920779 0.0291999999829908 0.0439999999743696 0.0461999999730883 0.0241999999859033 0 0.0288 0.0044 0.0038 0.0058 0.0136 0.0292 0.044 0.0462 0.0242 0.0288 0.0044 0.0038 0.0058 0.0136 0.0292 0.044 0.0462 0.0242 0.0288 0.0044 0.0038 0.0058 0.0136 0.0292 0.044 0.0462 0.0242 0.0288 0.0044 0.0038 0.0058 0.0136 0.0292 0.044 0.0462 0.0242 0.0288 0.0044 0.0038 0.0058 0.0136 0.0292 0.044 0.0462 0.0242 0.0288 0.0044 0.0038 0.0058 0.0136 0.0292 0.044 0.0462 0.0242 0.0288 0.0044 0.0038 0.0058 0.0136 0.0292 0.044 0.0462 0.0242 0.0288 0.0044 0.0038 0.0058 0.0136 0.0292 0.044 0.0462 0.0242 0.0288 0.0044 0.0038 0.0058 0.0136 0.0292 0.044 0.0462 0.0242 0.0288 0.0044 0.0038 0.0058 0.0136 0.0292 0.044 0.0462 0.0242 |
|
|
|
|
Hi Tri,
OK, in the post above is ONE line from the grain file. THe best way to understand it is to run the model then have a look at the grain.txt file that CAESAR saves every 100 iterations.
To explain, the first three numbers are the x and y co-ordinates and the third is an index number (do not worry, this is re-set when CAESAR loads the data, so can be any number as long as it is an integer).
Then follow 11 numbers:
0 0.0287999999832238 0.00439999999743697 0.00379999999778647 0.00579999999662147 0.0135999999920779 0.0291999999829908 0.0439999999743696 0.0461999999730883 0.0241999999859033 0
these are 0, then the total elevations of each of the 9 grainsizes for the SURFACE layer, then another 0. The 0 at each end was from a time when the model had a value for vegetation levels and the last one for bedrock levels. Veg and bedrock are now handled differently, but I left them in there so the model can read old files. So this line sets up the grainsize fractions for the surface (the grain[x,y,0] array in the code).
Next there are 9 numbers:
0.0288 0.0044 0.0038 0.0058 0.0136 0.0292 0.044 0.0462 0.0242
THese are the elevations for the 9 grainsizes in the next layer down - which is placed into the strata array in the code. (by elevations I mean the thickness of each grain fraction in the layer. If you multiply them by the grid size^2 then you get the volume). THen there are 8 further sequences of the same 9 numbers - which are for the next 8 layers down. For other cells, wheere there has been more erosion and deposition these values will probably change - as the sediment values sub surface will change.
So for each grid cell where there has been erosion and deposition, there are c.100 values!
Tom |
|
|
|
|
I put this in a separate post to make things easier!
Now to create your own grain size file is possible, but you probably need to write a simple program to do this.
What I tend to do is put in average distributions for the reach, then run the model for a while and the model will then erode/deposit and create its own grainsize distribution - part of the spin up process.
Tom |
|
|
| Back to top |
|
