You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The abstract class error looks like the DigitalCommsWrapper hasn't fully implemented the
SectorModel interface.
The data interfaces for smif have also been changing faster than the sector model prototypes.
Over the next 3-6months each model should be getting to a more mature state and integration
will be a focus over that time.
The configuration errors relate to the scenario data format, which is another area under active
development as Craig Robson (Newcastle) is working on the database backend to have as
alternative option to our first-prototype YAML file inputs.
E TypeError: Can't instantiate abstract class DigitalCommsWrapper with abstract methods
initialise /usr/local/lib/python3.5/dist-packages/smif/sector_model.py:243: TypeError
The model configuration was invalid
Captured stderr call
ERROR Expected a
value for 'interval' in each data point in a scenario, only received {'region': 'England',
'year': 2010, 'units': 'people', 'value': 52000000} ERROR Expected a value for 'interval' in
each data point in a scenario, only received {'region': 'Scotland', 'year': 2010, 'units':
'people', 'value': 5100000}
The text was updated successfully, but these errors were encountered:
Child of #55
Tasks:
See nismod-2 errors on master checkout
integration tests to pass
email Ron Fowler at STFC
The abstract class error looks like the DigitalCommsWrapper hasn't fully implemented the
SectorModel interface.
The data interfaces for smif have also been changing faster than the sector model prototypes.
Over the next 3-6months each model should be getting to a more mature state and integration
will be a focus over that time.
The configuration errors relate to the scenario data format, which is another area under active
development as Craig Robson (Newcastle) is working on the database backend to have as
alternative option to our first-prototype YAML file inputs.
The text was updated successfully, but these errors were encountered: