TUFLOW Message 0100: Difference between revisions

Content deleted Content added
Created page with '{{TUFLOW_Message |tuflow_message=ERROR 0100 - A "BC DATABASE" command must occur before a "READ BC" command |alt_msg=NA |type=ERROR |message_desc=???? |suggestions=???? |disc...'
 
No edit summary
 
(8 intermediate revisions by 3 users not shown)
Line 1:
{{TUFLOW_Message
|tuflow_message=ERROR 0100 - A "<font color="blue"><tt>BC DATABASEDatabase</tt></font>" command must occur before a "READ<font color="blue"><tt>Read BC</tt></font>" command
|alt_msg=NA
|type=[[ERROR]]
|message_desc=A <font color="blue"><tt>BC Database </tt></font>command must occur prior to any 1D (.ecf) and 2D (.tbc) <font color="blue"><tt>Read GIS BC </tt></font>command(s).
|message_desc=????
 
|suggestions=????
The reason for this is that <font color="blue"><tt>BC Database </tt></font> can be specified any number of times, with the most recent occurrence being used to set the active database when a <font color="blue"><tt>Read GIS BC </tt></font> command occurs. This was used by modellers as a way of applying different events or probabilities to different boundaries. If using the 2010-10 release or later, it is recommended to switch to the new event management feature as this is much more flexible and intuitive (refer to the <u>[https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW Manual]</u>).<br>
|discussion_page=* [[Talk:TUFLOW Message 0100|Discuss Message 0100]]
This error can occur if bc_dbase is listed under a scenario/event block, but incorrect scenario/event is specified and the simulation runs without bc_dbase.
|link3=''
|suggestions=Check the <font color="blue"><tt>BC Database </tt></font>command occurs before any <font color="blue"><tt>Read GIS BC </tt></font> commands. If there is no <font color="blue"><tt>BC Database </tt></font>command one will need to be specified (unless there are no boundaries, ie. no <font color="blue"><tt>Read GIS BC </tt></font> commands).
|link4=''
<br>
|prelink=[[TUFLOW_Message_0041|Message 0041]]
 
|uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]]
|nextlink=[[TUFLOW_Message_0101|Message 0101]]
}}