Revision as of 13:52, 5 February 2019 view source ShuangGao (talk \| contribs) Bureaucrats, Administrators 1,087 edits No edit summary ← Older edit		Revision as of 13:54, 5 February 2019 view source ShuangGao (talk \| contribs) Bureaucrats, Administrators 1,087 edits No edit summary Newer edit →
Line 13: ''Infrequent licence checks:''<br> If you have checked all the connectivity issues and the problem still persists, this could be caused by licence ~~checks~~ being checked too ~~infrequent~~infrequently. Prior to built 2018-03-AA the licence could get lost for HPC/GPU runs when the map output was very infrequent. This could cause TUFLOW to drop the licence and attempt to re-take the licence after a long period. A bug fix has been introduced for this in the 2018-03-AA build and later. But rarely, the licence can still get lost if the map output is infrequent, plus the model does not have ANY 1D or hidden 1D structures (e.g. a QT boundary). As a workaround: * Include more frequent map output, possibly within an small dummy output zone to avoid large outputs. * Include a dummy 1D channel to invoke the more frequent licence checks.

TUFLOW Message 0935: Difference between revisions