@@ -317,14 +317,17 @@ def test_dim_nonmonotonic(self):
317
317
self .check_result (result , "aux" )
318
318
319
319
def test_dim_fails_typeident (self ):
320
- # The coord variable is identified as a CFDimensionCoordinate by cf.py,
321
- # but having the wrong units causes it to fail the 'is_time' or
322
- # 'is_period' test, so the 'provides_coord' rule fails to trigger.
323
- # So it is built as a 'miscellaneous' dim-coord.
320
+ # Provide a coord variable, identified as a CFDimensionCoordinate by
321
+ # cf.py, but with the "wrong" units for a time or period coord.
322
+ # This causes it to fail both 'is_time' and 'is_period' tests and so,
323
+ # within the 'action_provides_coordinate' routine, does not trigger as
324
+ # a 'provides_coord_(time[[_period]])' rule, but instead as a
325
+ # 'default_coordinate_(provide-phase)'.
326
+ # As a result, it is built as a 'miscellaneous' dim-coord.
324
327
# N.B. this makes *no* practical difference, because a 'misc' dim
325
- # coord is still a dim coord (albeit one with bad units).
326
- # ( N.B.#2 Not quite the same for lat/lon coords, where coord-specific
327
- # 'build' rules always use a fixed standard-name ) .
328
+ # coord is still a dim coord (albeit one with incorrect units).
329
+ # N.B.#2 that is different from lat/lon coords, where the coord-specific
330
+ # 'build' rules have the extra effect of setting a fixed standard-name.
328
331
#
329
332
# Rules Triggered:
330
333
# 001 : fc_default
@@ -391,6 +394,7 @@ def test_aux_fails_typeident(self):
391
394
class Test__time (Mixin__singlecoord__tests , tests .IrisTest ):
392
395
# Run 'time' coord tests
393
396
which = "time"
397
+ debug = True
394
398
395
399
@classmethod
396
400
def setUpClass (cls ):
0 commit comments