Changeset 2900
- Timestamp:
- May 17, 2006, 5:28:15 PM (19 years ago)
- Location:
- production
- Files:
-
- 2 deleted
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
production/onslow_2006/make_report.py
r2898 r2900 35 35 some of the core inputs are already in place 36 36 * an results.tex file needs to be written for the particular scenario 37 * any data issues must be included in data_issues.tex (data.tex should38 be revised for future reports)39 37 * the tsunami-genic event should be discussed in tsunami_scenario.tex 40 38 * a summary must be written into summary.tex … … 97 95 % some of the core inputs are already in place 98 96 % * an results.tex file needs to be written for the particular scenario 99 % * any data issues must be included in data_issues.tex (data.tex should100 % be revised for future reports)101 97 % * the tsunami-genic event should be discussed in tsunami_scenario.tex 102 98 % * a summary must be written into summary.tex -
production/pt_hedland_2006/data.tex
r2869 r2900 46 46 by WA Department of Planning and Infrastructure. 47 47 48 \input{data_issues}49 50 48 The extent of the 51 49 data used for the tsunami impact modelling can be seen in the -
production/pt_hedland_2006/make_report.py
r2898 r2900 35 35 some of the core inputs are already in place 36 36 * an results.tex file needs to be written for the particular scenario 37 * any data issues must be included in data_issues.tex (data.tex should38 be revised for future reports)39 37 * the tsunami-genic event should be discussed in tsunami_scenario.tex 40 38 * a summary must be written into summary.tex … … 94 92 % some of the core inputs are already in place 95 93 % * an results.tex file needs to be written for the particular scenario 96 % * any data issues must be included in data_issues.tex (data.tex should97 % be revised for future reports)98 94 % * the tsunami-genic event should be discussed in tsunami_scenario.tex 99 95 % * a summary must be written into summary.tex
Note: See TracChangeset
for help on using the changeset viewer.