Change default of journey level config

tm2py/config.py

@@ -1161,15 +1161,15 @@ class ManualJourneyLevelsConfig(ConfigItem):
 @dataclass(frozen=True)
 class TransitJourneyLevelsConfig(ConfigItem):
     """Transit manual journey levels structure."""
-    use_algorithm: bool = True
+    use_algorithm: bool = False
     """
     The original translation from Cube to Emme used an algorithm to, as faithfully as possible, reflect transfer fares via journey levels. 
     The algorithm examines fare costs and proximity of transit services to create a set of journey levels that reflects transfer costs. 
     While this algorithm works well, the Bay Area's complex fare system results in numerous journey levels specific to operators with low ridership. 
     The resulting assignment compute therefore expends a lot of resources on these operators. 
     Set this parameter to `True` to use the algorithm. Exactly one of `use_algorithm` or `specify_manually` must be `True`. 
     """
-    specify_manually: bool = False
+    specify_manually: bool = True
     """
     An alternative to using an algorithm to specify the journey levels is to use specify them manually. 
     If this option is set to `True`, the `manual` parameter can be used to assign fare systems to faresystem groups (or journey levels). 
@@ -1178,7 +1178,7 @@ class TransitJourneyLevelsConfig(ConfigItem):
     The other faresystem group is automatically generated in the code with the rest of the faresystems which are not specified in any of the groups.
     See the `manual` entry for an example.
     """ 
-    manual: Optional[Tuple[ManualJourneyLevelsConfig, ...]] = None
+    manual: Optional[Tuple[ManualJourneyLevelsConfig, ...]] = (ManualJourneyLevelsConfig(level_id=1, group_fare_systems=(25,)),)
     """
     If 'specify_manually' is set to `True`, there should be at least one faresystem group specified here.
     The format includes two entries: `level_id`, which is the serial number of the group specified,