blakeblackshear/frigate

14→4 frigate.config.camera.detect uses frigate.config.base✕

Connections

3 pairs of types, where a type in frigate.config.camera.detect uses a type in frigate.config.base.

The types involved

• frigate.config.camera.detect.DetectConfig → frigate.config.base.FrigateBaseModel
• frigate.config.camera.detect.StationaryConfig → frigate.config.base.FrigateBaseModel
• frigate.config.camera.detect.StationaryMaxFramesConfig → frigate.config.base.FrigateBaseModel

Direction

frigate.config.camera.detect uses frigate.config.base, so a change to frigate.config.base can break frigate.config.camera.detect, while a change to frigate.config.camera.detect can't break frigate.config.base.

Position

Below the diagonal: frigate.config.camera.detect uses a module listed above it, which is the healthy direction.

15→4 frigate.config.camera.ffmpeg uses frigate.config.base✕

Connections

3 pairs of types, where a type in frigate.config.camera.ffmpeg uses a type in frigate.config.base.

The types involved

• frigate.config.camera.ffmpeg.CameraInput → frigate.config.base.FrigateBaseModel
• frigate.config.camera.ffmpeg.FfmpegConfig → frigate.config.base.FrigateBaseModel
• frigate.config.camera.ffmpeg.FfmpegOutputArgsConfig → frigate.config.base.FrigateBaseModel

Direction

frigate.config.camera.ffmpeg uses frigate.config.base, so a change to frigate.config.base can break frigate.config.camera.ffmpeg, while a change to frigate.config.camera.ffmpeg can't break frigate.config.base.

Position

Below the diagonal: frigate.config.camera.ffmpeg uses a module listed above it, which is the healthy direction.

16→4 frigate.config.camera.record uses frigate.config.base✕

Connections

7 pairs of types, where a type in frigate.config.camera.record uses a type in frigate.config.base.

The types involved

• frigate.config.camera.record.EventsConfig → frigate.config.base.FrigateBaseModel
• frigate.config.camera.record.RecordConfig → frigate.config.base.FrigateBaseModel
• frigate.config.camera.record.RecordExportConfig → frigate.config.base.FrigateBaseModel
• frigate.config.camera.record.RecordPreviewConfig → frigate.config.base.FrigateBaseModel
• frigate.config.camera.record.RecordRetainConfig → frigate.config.base.FrigateBaseModel
• frigate.config.camera.record.RecordSubConfig → frigate.config.base.FrigateBaseModel
• frigate.config.camera.record.ReviewRetainConfig → frigate.config.base.FrigateBaseModel

Direction

frigate.config.camera.record uses frigate.config.base, so a change to frigate.config.base can break frigate.config.camera.record, while a change to frigate.config.camera.record can't break frigate.config.base.

Position

Below the diagonal: frigate.config.camera.record uses a module listed above it, which is the healthy direction.

17→4 frigate.config.classification uses frigate.config.base✕

Connections

16 pairs of types, where a type in frigate.config.classification uses a type in frigate.config.base.

The types involved

• frigate.config.classification.AudioTranscriptionConfig → frigate.config.base.FrigateBaseModel
• frigate.config.classification.BirdClassificationConfig → frigate.config.base.FrigateBaseModel
• frigate.config.classification.CameraAudioTranscriptionConfig → frigate.config.base.FrigateBaseModel
• frigate.config.classification.CameraFaceRecognitionConfig → frigate.config.base.FrigateBaseModel
• frigate.config.classification.CameraLicensePlateRecognitionConfig → frigate.config.base.FrigateBaseModel
• frigate.config.classification.CameraSemanticSearchConfig → frigate.config.base.FrigateBaseModel
• frigate.config.classification.ClassificationConfig → frigate.config.base.FrigateBaseModel
• frigate.config.classification.CustomClassificationConfig → frigate.config.base.FrigateBaseModel
• frigate.config.classification.CustomClassificationObjectConfig → frigate.config.base.FrigateBaseModel
• frigate.config.classification.CustomClassificationStateCameraConfig → frigate.config.base.FrigateBaseModel
• frigate.config.classification.CustomClassificationStateConfig → frigate.config.base.FrigateBaseModel
• frigate.config.classification.FaceRecognitionConfig → frigate.config.base.FrigateBaseModel
• frigate.config.classification.LicensePlateRecognitionConfig → frigate.config.base.FrigateBaseModel
• frigate.config.classification.ReplaceRule → frigate.config.base.FrigateBaseModel
• frigate.config.classification.SemanticSearchConfig → frigate.config.base.FrigateBaseModel
• frigate.config.classification.TriggerConfig → frigate.config.base.FrigateBaseModel

Direction

frigate.config.classification uses frigate.config.base, so a change to frigate.config.base can break frigate.config.classification, while a change to frigate.config.classification can't break frigate.config.base.

Position

Below the diagonal: frigate.config.classification uses a module listed above it, which is the healthy direction.

18→7 frigate.detectors.detection_api uses frigate.detectors.detector_config✕

Connections

1 pair of types, where a type in frigate.detectors.detection_api uses a type in frigate.detectors.detector_config.

The types involved

• frigate.detectors.detection_api.DetectionApi → frigate.detectors.detector_config.BaseDetectorConfig

Direction

frigate.detectors.detection_api uses frigate.detectors.detector_config, so a change to frigate.detectors.detector_config can break frigate.detectors.detection_api, while a change to frigate.detectors.detection_api can't break frigate.detectors.detector_config.

Position

Below the diagonal: frigate.detectors.detection_api uses a module listed above it, which is the healthy direction.

19→4 frigate.config.camera.camera uses frigate.config.base✕

Connections

1 pair of types, where a type in frigate.config.camera.camera uses a type in frigate.config.base.

The types involved

• frigate.config.camera.camera.CameraConfig → frigate.config.base.FrigateBaseModel

Direction

frigate.config.camera.camera uses frigate.config.base, so a change to frigate.config.base can break frigate.config.camera.camera, while a change to frigate.config.camera.camera can't break frigate.config.base.

Position

Below the diagonal: frigate.config.camera.camera uses a module listed above it, which is the healthy direction.

19→14 frigate.config.camera.camera uses frigate.config.camera.detect✕

Connections

1 pair of types, where a type in frigate.config.camera.camera uses a type in frigate.config.camera.detect.

The types involved

• frigate.config.camera.camera.CameraConfig → frigate.config.camera.detect.DetectConfig

Direction

frigate.config.camera.camera uses frigate.config.camera.detect, so a change to frigate.config.camera.detect can break frigate.config.camera.camera, while a change to frigate.config.camera.camera can't break frigate.config.camera.detect.

Position

Below the diagonal: frigate.config.camera.camera uses a module listed above it, which is the healthy direction.

19→15 frigate.config.camera.camera uses frigate.config.camera.ffmpeg✕

Connections

2 pairs of types, where a type in frigate.config.camera.camera uses a type in frigate.config.camera.ffmpeg.

The types involved

• frigate.config.camera.camera.CameraConfig → frigate.config.camera.ffmpeg.CameraFfmpegConfig
• frigate.config.camera.camera.CameraConfig → frigate.config.camera.ffmpeg.CameraInput

Direction

frigate.config.camera.camera uses frigate.config.camera.ffmpeg, so a change to frigate.config.camera.ffmpeg can break frigate.config.camera.camera, while a change to frigate.config.camera.camera can't break frigate.config.camera.ffmpeg.

Position

Below the diagonal: frigate.config.camera.camera uses a module listed above it, which is the healthy direction.

19→16 frigate.config.camera.camera uses frigate.config.camera.record✕

Connections

1 pair of types, where a type in frigate.config.camera.camera uses a type in frigate.config.camera.record.

The types involved

• frigate.config.camera.camera.CameraConfig → frigate.config.camera.record.RecordConfig

Direction

frigate.config.camera.camera uses frigate.config.camera.record, so a change to frigate.config.camera.record can break frigate.config.camera.camera, while a change to frigate.config.camera.camera can't break frigate.config.camera.record.

Position

Below the diagonal: frigate.config.camera.camera uses a module listed above it, which is the healthy direction.

19→17 frigate.config.camera.camera uses frigate.config.classification✕

Connections

4 pairs of types, where a type in frigate.config.camera.camera uses a type in frigate.config.classification.

The types involved

• frigate.config.camera.camera.CameraConfig → frigate.config.classification.CameraAudioTranscriptionConfig
• frigate.config.camera.camera.CameraConfig → frigate.config.classification.CameraFaceRecognitionConfig
• frigate.config.camera.camera.CameraConfig → frigate.config.classification.CameraLicensePlateRecognitionConfig
• frigate.config.camera.camera.CameraConfig → frigate.config.classification.CameraSemanticSearchConfig

Direction

frigate.config.camera.camera uses frigate.config.classification, so a change to frigate.config.classification can break frigate.config.camera.camera, while a change to frigate.config.camera.camera can't break frigate.config.classification.

Position

Below the diagonal: frigate.config.camera.camera uses a module listed above it, which is the healthy direction.

20→4 frigate.config.config uses frigate.config.base✕

Connections

1 pair of types, where a type in frigate.config.config uses a type in frigate.config.base.

The types involved

• frigate.config.config.FrigateConfig → frigate.config.base.FrigateBaseModel

Direction

frigate.config.config uses frigate.config.base, so a change to frigate.config.base can break frigate.config.config, while a change to frigate.config.config can't break frigate.config.base.

Position

Below the diagonal: frigate.config.config uses a module listed above it, which is the healthy direction.

20→7 frigate.config.config uses frigate.detectors.detector_config✕

Connections

1 pair of types, where a type in frigate.config.config uses a type in frigate.detectors.detector_config.

The types involved

• frigate.config.config.FrigateConfig → frigate.detectors.detector_config.ModelConfig

Direction

frigate.config.config uses frigate.detectors.detector_config, so a change to frigate.detectors.detector_config can break frigate.config.config, while a change to frigate.config.config can't break frigate.detectors.detector_config.

Position

Below the diagonal: frigate.config.config uses a module listed above it, which is the healthy direction.

20→14 frigate.config.config uses frigate.config.camera.detect✕

Connections

1 pair of types, where a type in frigate.config.config uses a type in frigate.config.camera.detect.

The types involved

• frigate.config.config.FrigateConfig → frigate.config.camera.detect.DetectConfig

Direction

frigate.config.config uses frigate.config.camera.detect, so a change to frigate.config.camera.detect can break frigate.config.config, while a change to frigate.config.config can't break frigate.config.camera.detect.

Position

Below the diagonal: frigate.config.config uses a module listed above it, which is the healthy direction.

20→15 frigate.config.config uses frigate.config.camera.ffmpeg✕

Connections

1 pair of types, where a type in frigate.config.config uses a type in frigate.config.camera.ffmpeg.

The types involved

• frigate.config.config.FrigateConfig → frigate.config.camera.ffmpeg.FfmpegConfig

Direction

frigate.config.config uses frigate.config.camera.ffmpeg, so a change to frigate.config.camera.ffmpeg can break frigate.config.config, while a change to frigate.config.config can't break frigate.config.camera.ffmpeg.

Position

Below the diagonal: frigate.config.config uses a module listed above it, which is the healthy direction.

20→16 frigate.config.config uses frigate.config.camera.record✕

Connections

1 pair of types, where a type in frigate.config.config uses a type in frigate.config.camera.record.

The types involved

• frigate.config.config.FrigateConfig → frigate.config.camera.record.RecordConfig

Direction

frigate.config.config uses frigate.config.camera.record, so a change to frigate.config.camera.record can break frigate.config.config, while a change to frigate.config.config can't break frigate.config.camera.record.

Position

Below the diagonal: frigate.config.config uses a module listed above it, which is the healthy direction.

20→17 frigate.config.config uses frigate.config.classification✕

Connections

5 pairs of types, where a type in frigate.config.config uses a type in frigate.config.classification.

The types involved

• frigate.config.config.FrigateConfig → frigate.config.classification.AudioTranscriptionConfig
• frigate.config.config.FrigateConfig → frigate.config.classification.ClassificationConfig
• frigate.config.config.FrigateConfig → frigate.config.classification.FaceRecognitionConfig
• frigate.config.config.FrigateConfig → frigate.config.classification.LicensePlateRecognitionConfig
• frigate.config.config.FrigateConfig → frigate.config.classification.SemanticSearchConfig

Direction

frigate.config.config uses frigate.config.classification, so a change to frigate.config.classification can break frigate.config.config, while a change to frigate.config.config can't break frigate.config.classification.

Position

Below the diagonal: frigate.config.config uses a module listed above it, which is the healthy direction.

21→5 frigate uses frigate.config.camera.updater✕

Connections

1 pair of types, where a type in frigate uses a type in frigate.config.camera.updater.

The types involved

• frigate.debug_replay → frigate.config.camera.updater.CameraConfigUpdatePublisher

Direction

frigate uses frigate.config.camera.updater, so a change to frigate.config.camera.updater can break frigate, while a change to frigate can't break frigate.config.camera.updater.

Position

Below the diagonal: frigate uses a module listed above it, which is the healthy direction.

21→20 frigate uses frigate.config.config✕

Connections

1 pair of types, where a type in frigate uses a type in frigate.config.config.

The types involved

• frigate.debug_replay → frigate.config.config.FrigateConfig

Direction

frigate uses frigate.config.config, so a change to frigate.config.config can break frigate, while a change to frigate can't break frigate.config.config.

Position

Below the diagonal: frigate uses a module listed above it, which is the healthy direction.

22→5 frigate.comms.dispatcher uses frigate.config.camera.updater✕

Connections

1 pair of types, where a type in frigate.comms.dispatcher uses a type in frigate.config.camera.updater.

The types involved

• frigate.comms.dispatcher.Dispatcher → frigate.config.camera.updater.CameraConfigUpdatePublisher

Direction

frigate.comms.dispatcher uses frigate.config.camera.updater, so a change to frigate.config.camera.updater can break frigate.comms.dispatcher, while a change to frigate.comms.dispatcher can't break frigate.config.camera.updater.

Position

Below the diagonal: frigate.comms.dispatcher uses a module listed above it, which is the healthy direction.

22→20 frigate.comms.dispatcher uses frigate.config.config✕

Connections

1 pair of types, where a type in frigate.comms.dispatcher uses a type in frigate.config.config.

The types involved

• frigate.comms.dispatcher.Dispatcher → frigate.config.config.FrigateConfig

Direction

frigate.comms.dispatcher uses frigate.config.config, so a change to frigate.config.config can break frigate.comms.dispatcher, while a change to frigate.comms.dispatcher can't break frigate.config.config.

Position

Below the diagonal: frigate.comms.dispatcher uses a module listed above it, which is the healthy direction.

23→2 frigate.data_processing.common.license_plate.mixin uses frigate.comms.event_metadata_updater✕

Connections

1 pair of types, where a type in frigate.data_processing.common.license_plate.mixin uses a type in frigate.comms.event_metadata_updater.

The types involved

• frigate.data_processing.common.license_plate.mixin.LicensePlateProcessingMixin → frigate.comms.event_metadata_updater.EventMetadataPublisher

Direction

frigate.data_processing.common.license_plate.mixin uses frigate.comms.event_metadata_updater, so a change to frigate.comms.event_metadata_updater can break frigate.data_processing.common.license_plate.mixin, while a change to frigate.data_processing.common.license_plate.mixin can't break frigate.comms.event_metadata_updater.

Position

Below the diagonal: frigate.data_processing.common.license_plate.mixin uses a module listed above it, which is the healthy direction.

23→3 frigate.data_processing.common.license_plate.mixin uses frigate.comms.inter_process✕

Connections

1 pair of types, where a type in frigate.data_processing.common.license_plate.mixin uses a type in frigate.comms.inter_process.

The types involved

• frigate.data_processing.common.license_plate.mixin.LicensePlateProcessingMixin → frigate.comms.inter_process.InterProcessRequestor

Direction

frigate.data_processing.common.license_plate.mixin uses frigate.comms.inter_process, so a change to frigate.comms.inter_process can break frigate.data_processing.common.license_plate.mixin, while a change to frigate.data_processing.common.license_plate.mixin can't break frigate.comms.inter_process.

Position

Below the diagonal: frigate.data_processing.common.license_plate.mixin uses a module listed above it, which is the healthy direction.

23→6 frigate.data_processing.common.license_plate.mixin uses frigate.data_processing.types✕

Connections

1 pair of types, where a type in frigate.data_processing.common.license_plate.mixin uses a type in frigate.data_processing.types.

The types involved

• frigate.data_processing.common.license_plate.mixin.LicensePlateProcessingMixin → frigate.data_processing.types.DataProcessorMetrics

Direction

frigate.data_processing.common.license_plate.mixin uses frigate.data_processing.types, so a change to frigate.data_processing.types can break frigate.data_processing.common.license_plate.mixin, while a change to frigate.data_processing.common.license_plate.mixin can't break frigate.data_processing.types.

Position

Below the diagonal: frigate.data_processing.common.license_plate.mixin uses a module listed above it, which is the healthy direction.

23→17 frigate.data_processing.common.license_plate.mixin uses frigate.config.classification✕

Connections

1 pair of types, where a type in frigate.data_processing.common.license_plate.mixin uses a type in frigate.config.classification.

The types involved

• frigate.data_processing.common.license_plate.mixin.LicensePlateProcessingMixin → frigate.config.classification.LicensePlateRecognitionConfig

Direction

frigate.data_processing.common.license_plate.mixin uses frigate.config.classification, so a change to frigate.config.classification can break frigate.data_processing.common.license_plate.mixin, while a change to frigate.data_processing.common.license_plate.mixin can't break frigate.config.classification.

Position

Below the diagonal: frigate.data_processing.common.license_plate.mixin uses a module listed above it, which is the healthy direction.

23→20 frigate.data_processing.common.license_plate.mixin uses frigate.config.config✕

Connections

1 pair of types, where a type in frigate.data_processing.common.license_plate.mixin uses a type in frigate.config.config.

The types involved

• frigate.data_processing.common.license_plate.mixin.LicensePlateProcessingMixin → frigate.config.config.FrigateConfig

Direction

frigate.data_processing.common.license_plate.mixin uses frigate.config.config, so a change to frigate.config.config can break frigate.data_processing.common.license_plate.mixin, while a change to frigate.data_processing.common.license_plate.mixin can't break frigate.config.config.

Position

Below the diagonal: frigate.data_processing.common.license_plate.mixin uses a module listed above it, which is the healthy direction.

24→6 frigate.data_processing.post.api uses frigate.data_processing.types✕

Connections

2 pairs of types, where a type in frigate.data_processing.post.api uses a type in frigate.data_processing.types.

The types involved

• frigate.data_processing.post.api.PostProcessorApi → frigate.data_processing.types.DataProcessorMetrics
• frigate.data_processing.post.api.PostProcessorApi → frigate.data_processing.types.PostProcessDataEnum

Direction

frigate.data_processing.post.api uses frigate.data_processing.types, so a change to frigate.data_processing.types can break frigate.data_processing.post.api, while a change to frigate.data_processing.post.api can't break frigate.data_processing.types.

Position

Below the diagonal: frigate.data_processing.post.api uses a module listed above it, which is the healthy direction.

24→20 frigate.data_processing.post.api uses frigate.config.config✕

Connections

1 pair of types, where a type in frigate.data_processing.post.api uses a type in frigate.config.config.

The types involved

• frigate.data_processing.post.api.PostProcessorApi → frigate.config.config.FrigateConfig

Direction

frigate.data_processing.post.api uses frigate.config.config, so a change to frigate.config.config can break frigate.data_processing.post.api, while a change to frigate.data_processing.post.api can't break frigate.config.config.

Position

Below the diagonal: frigate.data_processing.post.api uses a module listed above it, which is the healthy direction.

25→6 frigate.data_processing.real_time.api uses frigate.data_processing.types✕

Connections

2 pairs of types, where a type in frigate.data_processing.real_time.api uses a type in frigate.data_processing.types.

The types involved

• frigate.data_processing.real_time.api.DeferredRealtimeProcessorApi → frigate.data_processing.types.DataProcessorMetrics
• frigate.data_processing.real_time.api.RealTimeProcessorApi → frigate.data_processing.types.DataProcessorMetrics

Direction

frigate.data_processing.real_time.api uses frigate.data_processing.types, so a change to frigate.data_processing.types can break frigate.data_processing.real_time.api, while a change to frigate.data_processing.real_time.api can't break frigate.data_processing.types.

Position

Below the diagonal: frigate.data_processing.real_time.api uses a module listed above it, which is the healthy direction.

25→20 frigate.data_processing.real_time.api uses frigate.config.config✕

Connections

2 pairs of types, where a type in frigate.data_processing.real_time.api uses a type in frigate.config.config.

The types involved

• frigate.data_processing.real_time.api.DeferredRealtimeProcessorApi → frigate.config.config.FrigateConfig
• frigate.data_processing.real_time.api.RealTimeProcessorApi → frigate.config.config.FrigateConfig

Direction

frigate.data_processing.real_time.api uses frigate.config.config, so a change to frigate.config.config can break frigate.data_processing.real_time.api, while a change to frigate.data_processing.real_time.api can't break frigate.config.config.

Position

Below the diagonal: frigate.data_processing.real_time.api uses a module listed above it, which is the healthy direction.

26→9 frigate.genai uses frigate.models✕

Connections

2 pairs of types, where a type in frigate.genai uses a type in frigate.models.

The types involved

• frigate.genai.GenAIClient → frigate.models.Event
• frigate.genai.prompts → frigate.models.Event

Direction

frigate.genai uses frigate.models, so a change to frigate.models can break frigate.genai, while a change to frigate.genai can't break frigate.models.

Position

Below the diagonal: frigate.genai uses a module listed above it, which is the healthy direction.

26→19 frigate.genai uses frigate.config.camera.camera✕

Connections

2 pairs of types, where a type in frigate.genai uses a type in frigate.config.camera.camera.

The types involved

• frigate.genai.GenAIClient → frigate.config.camera.camera.CameraConfig
• frigate.genai.prompts → frigate.config.camera.camera.CameraConfig

Direction

frigate.genai uses frigate.config.camera.camera, so a change to frigate.config.camera.camera can break frigate.genai, while a change to frigate.genai can't break frigate.config.camera.camera.

Position

Below the diagonal: frigate.genai uses a module listed above it, which is the healthy direction.

26→20 frigate.genai uses frigate.config.config✕

Connections

1 pair of types, where a type in frigate.genai uses a type in frigate.config.config.

The types involved

• frigate.genai.prompts → frigate.config.config.FrigateConfig

Direction

frigate.genai uses frigate.config.config, so a change to frigate.config.config can break frigate.genai, while a change to frigate.genai can't break frigate.config.config.

Position

Below the diagonal: frigate.genai uses a module listed above it, which is the healthy direction.

27→5 frigate.jobs uses frigate.config.camera.updater✕

Connections

1 pair of types, where a type in frigate.jobs uses a type in frigate.config.camera.updater.

The types involved

• frigate.jobs.debug_replay → frigate.config.camera.updater.CameraConfigUpdatePublisher

Direction

frigate.jobs uses frigate.config.camera.updater, so a change to frigate.config.camera.updater can break frigate.jobs, while a change to frigate.jobs can't break frigate.config.camera.updater.

Position

Below the diagonal: frigate.jobs uses a module listed above it, which is the healthy direction.

27→8 frigate.jobs uses frigate.jobs.job✕

Connections

1 pair of types, where a type in frigate.jobs uses a type in frigate.jobs.job.

The types involved

• frigate.jobs.manager → frigate.jobs.job.Job

Direction

frigate.jobs uses frigate.jobs.job, so a change to frigate.jobs.job can break frigate.jobs, while a change to frigate.jobs can't break frigate.jobs.job.

Position

Below the diagonal: frigate.jobs uses a module listed above it, which is the healthy direction.

27→9 frigate.jobs uses frigate.models✕

Connections

1 pair of types, where a type in frigate.jobs uses a type in frigate.models.

The types involved

• frigate.jobs.motion_search → frigate.models.Recordings

Direction

frigate.jobs uses frigate.models, so a change to frigate.models can break frigate.jobs, while a change to frigate.jobs can't break frigate.models.

Position

Below the diagonal: frigate.jobs uses a module listed above it, which is the healthy direction.

27→19 frigate.jobs uses frigate.config.camera.camera✕

Connections

1 pair of types, where a type in frigate.jobs uses a type in frigate.config.camera.camera.

The types involved

• frigate.jobs.motion_search_decode → frigate.config.camera.camera.CameraConfig

Direction

frigate.jobs uses frigate.config.camera.camera, so a change to frigate.config.camera.camera can break frigate.jobs, while a change to frigate.jobs can't break frigate.config.camera.camera.

Position

Below the diagonal: frigate.jobs uses a module listed above it, which is the healthy direction.

27→20 frigate.jobs uses frigate.config.config✕

Connections

4 pairs of types, where a type in frigate.jobs uses a type in frigate.config.config.

The types involved

• frigate.jobs.debug_replay → frigate.config.config.FrigateConfig
• frigate.jobs.export → frigate.config.config.FrigateConfig
• frigate.jobs.motion_search → frigate.config.config.FrigateConfig
• frigate.jobs.vlm_watch → frigate.config.config.FrigateConfig

Direction

frigate.jobs uses frigate.config.config, so a change to frigate.config.config can break frigate.jobs, while a change to frigate.jobs can't break frigate.config.config.

Position

Below the diagonal: frigate.jobs uses a module listed above it, which is the healthy direction.

28→7 frigate.track.tracked_object uses frigate.detectors.detector_config✕

Connections

1 pair of types, where a type in frigate.track.tracked_object uses a type in frigate.detectors.detector_config.

The types involved

• frigate.track.tracked_object.TrackedObject → frigate.detectors.detector_config.ModelConfig

Direction

frigate.track.tracked_object uses frigate.detectors.detector_config, so a change to frigate.detectors.detector_config can break frigate.track.tracked_object, while a change to frigate.track.tracked_object can't break frigate.detectors.detector_config.

Position

Below the diagonal: frigate.track.tracked_object uses a module listed above it, which is the healthy direction.

28→19 frigate.track.tracked_object uses frigate.config.camera.camera✕

Connections

1 pair of types, where a type in frigate.track.tracked_object uses a type in frigate.config.camera.camera.

The types involved

• frigate.track.tracked_object.TrackedObject → frigate.config.camera.camera.CameraConfig

Direction

frigate.track.tracked_object uses frigate.config.camera.camera, so a change to frigate.config.camera.camera can break frigate.track.tracked_object, while a change to frigate.track.tracked_object can't break frigate.config.camera.camera.

Position

Below the diagonal: frigate.track.tracked_object uses a module listed above it, which is the healthy direction.

29→7 frigate.util uses frigate.detectors.detector_config✕

Connections

1 pair of types, where a type in frigate.util uses a type in frigate.detectors.detector_config.

The types involved

• frigate.util.object → frigate.detectors.detector_config.ModelConfig

Direction

frigate.util uses frigate.detectors.detector_config, so a change to frigate.detectors.detector_config can break frigate.util, while a change to frigate.util can't break frigate.detectors.detector_config.

Position

Below the diagonal: frigate.util uses a module listed above it, which is the healthy direction.

29→9 frigate.util uses frigate.models✕

Connections

2 pairs of types, where a type in frigate.util uses a type in frigate.models.

The types involved

• frigate.util.classification → frigate.models.Event
• frigate.util.file → frigate.models.Event

Direction

frigate.util uses frigate.models, so a change to frigate.models can break frigate.util, while a change to frigate.util can't break frigate.models.

Position

Below the diagonal: frigate.util uses a module listed above it, which is the healthy direction.

29→14 frigate.util uses frigate.config.camera.detect✕

Connections

1 pair of types, where a type in frigate.util uses a type in frigate.config.camera.detect.

The types involved

• frigate.util.object → frigate.config.camera.detect.DetectConfig

Direction

frigate.util uses frigate.config.camera.detect, so a change to frigate.config.camera.detect can break frigate.util, while a change to frigate.util can't break frigate.config.camera.detect.

Position

Below the diagonal: frigate.util uses a module listed above it, which is the healthy direction.

29→20 frigate.util uses frigate.config.config✕

Connections

1 pair of types, where a type in frigate.util uses a type in frigate.config.config.

The types involved

• frigate.util.object_names → frigate.config.config.FrigateConfig

Direction

frigate.util uses frigate.config.config, so a change to frigate.config.config can break frigate.util, while a change to frigate.util can't break frigate.config.config.

Position

Below the diagonal: frigate.util uses a module listed above it, which is the healthy direction.

30→2 frigate.data_processing.post.license_plate uses frigate.comms.event_metadata_updater✕

Connections

1 pair of types, where a type in frigate.data_processing.post.license_plate uses a type in frigate.comms.event_metadata_updater.

The types involved

• frigate.data_processing.post.license_plate.LicensePlatePostProcessor → frigate.comms.event_metadata_updater.EventMetadataPublisher

Direction

frigate.data_processing.post.license_plate uses frigate.comms.event_metadata_updater, so a change to frigate.comms.event_metadata_updater can break frigate.data_processing.post.license_plate, while a change to frigate.data_processing.post.license_plate can't break frigate.comms.event_metadata_updater.

Position

Below the diagonal: frigate.data_processing.post.license_plate uses a module listed above it, which is the healthy direction.

30→3 frigate.data_processing.post.license_plate uses frigate.comms.inter_process✕

Connections

1 pair of types, where a type in frigate.data_processing.post.license_plate uses a type in frigate.comms.inter_process.

The types involved

• frigate.data_processing.post.license_plate.LicensePlatePostProcessor → frigate.comms.inter_process.InterProcessRequestor

Direction

frigate.data_processing.post.license_plate uses frigate.comms.inter_process, so a change to frigate.comms.inter_process can break frigate.data_processing.post.license_plate, while a change to frigate.data_processing.post.license_plate can't break frigate.comms.inter_process.

Position

Below the diagonal: frigate.data_processing.post.license_plate uses a module listed above it, which is the healthy direction.

30→6 frigate.data_processing.post.license_plate uses frigate.data_processing.types✕

Connections

2 pairs of types, where a type in frigate.data_processing.post.license_plate uses a type in frigate.data_processing.types.

The types involved

• frigate.data_processing.post.license_plate.LicensePlatePostProcessor → frigate.data_processing.types.DataProcessorMetrics
• frigate.data_processing.post.license_plate.LicensePlatePostProcessor → frigate.data_processing.types.PostProcessDataEnum

Direction

frigate.data_processing.post.license_plate uses frigate.data_processing.types, so a change to frigate.data_processing.types can break frigate.data_processing.post.license_plate, while a change to frigate.data_processing.post.license_plate can't break frigate.data_processing.types.

Position

Below the diagonal: frigate.data_processing.post.license_plate uses a module listed above it, which is the healthy direction.

30→20 frigate.data_processing.post.license_plate uses frigate.config.config✕

Connections

1 pair of types, where a type in frigate.data_processing.post.license_plate uses a type in frigate.config.config.

The types involved

• frigate.data_processing.post.license_plate.LicensePlatePostProcessor → frigate.config.config.FrigateConfig

Direction

frigate.data_processing.post.license_plate uses frigate.config.config, so a change to frigate.config.config can break frigate.data_processing.post.license_plate, while a change to frigate.data_processing.post.license_plate can't break frigate.config.config.

Position

Below the diagonal: frigate.data_processing.post.license_plate uses a module listed above it, which is the healthy direction.

30→23 frigate.data_processing.post.license_plate uses frigate.data_processing.common.license_plate.mixin✕

Connections

1 pair of types, where a type in frigate.data_processing.post.license_plate uses a type in frigate.data_processing.common.license_plate.mixin.

The types involved

• frigate.data_processing.post.license_plate.LicensePlatePostProcessor → frigate.data_processing.common.license_plate.mixin.LicensePlateProcessingMixin

Direction

frigate.data_processing.post.license_plate uses frigate.data_processing.common.license_plate.mixin, so a change to frigate.data_processing.common.license_plate.mixin can break frigate.data_processing.post.license_plate, while a change to frigate.data_processing.post.license_plate can't break frigate.data_processing.common.license_plate.mixin.

Position

Below the diagonal: frigate.data_processing.post.license_plate uses a module listed above it, which is the healthy direction.

30→24 frigate.data_processing.post.license_plate uses frigate.data_processing.post.api✕

Connections

1 pair of types, where a type in frigate.data_processing.post.license_plate uses a type in frigate.data_processing.post.api.

The types involved

• frigate.data_processing.post.license_plate.LicensePlatePostProcessor → frigate.data_processing.post.api.PostProcessorApi

Direction

frigate.data_processing.post.license_plate uses frigate.data_processing.post.api, so a change to frigate.data_processing.post.api can break frigate.data_processing.post.license_plate, while a change to frigate.data_processing.post.license_plate can't break frigate.data_processing.post.api.

Position

Below the diagonal: frigate.data_processing.post.license_plate uses a module listed above it, which is the healthy direction.

31→3 frigate.data_processing.post.object_descriptions uses frigate.comms.inter_process✕

Connections

1 pair of types, where a type in frigate.data_processing.post.object_descriptions uses a type in frigate.comms.inter_process.

The types involved

• frigate.data_processing.post.object_descriptions.ObjectDescriptionProcessor → frigate.comms.inter_process.InterProcessRequestor

Direction

frigate.data_processing.post.object_descriptions uses frigate.comms.inter_process, so a change to frigate.comms.inter_process can break frigate.data_processing.post.object_descriptions, while a change to frigate.data_processing.post.object_descriptions can't break frigate.comms.inter_process.

Position

Below the diagonal: frigate.data_processing.post.object_descriptions uses a module listed above it, which is the healthy direction.

31→6 frigate.data_processing.post.object_descriptions uses frigate.data_processing.types✕

Connections

2 pairs of types, where a type in frigate.data_processing.post.object_descriptions uses a type in frigate.data_processing.types.

The types involved

• frigate.data_processing.post.object_descriptions.ObjectDescriptionProcessor → frigate.data_processing.types.DataProcessorMetrics
• frigate.data_processing.post.object_descriptions.ObjectDescriptionProcessor → frigate.data_processing.types.PostProcessDataEnum

Direction

frigate.data_processing.post.object_descriptions uses frigate.data_processing.types, so a change to frigate.data_processing.types can break frigate.data_processing.post.object_descriptions, while a change to frigate.data_processing.post.object_descriptions can't break frigate.data_processing.types.

Position

Below the diagonal: frigate.data_processing.post.object_descriptions uses a module listed above it, which is the healthy direction.

31→9 frigate.data_processing.post.object_descriptions uses frigate.models✕

Connections

1 pair of types, where a type in frigate.data_processing.post.object_descriptions uses a type in frigate.models.

The types involved

• frigate.data_processing.post.object_descriptions.ObjectDescriptionProcessor → frigate.models.Event

Direction

frigate.data_processing.post.object_descriptions uses frigate.models, so a change to frigate.models can break frigate.data_processing.post.object_descriptions, while a change to frigate.data_processing.post.object_descriptions can't break frigate.models.

Position

Below the diagonal: frigate.data_processing.post.object_descriptions uses a module listed above it, which is the healthy direction.

31→19 frigate.data_processing.post.object_descriptions uses frigate.config.camera.camera✕

Connections

1 pair of types, where a type in frigate.data_processing.post.object_descriptions uses a type in frigate.config.camera.camera.

The types involved

• frigate.data_processing.post.object_descriptions.ObjectDescriptionProcessor → frigate.config.camera.camera.CameraConfig

Direction

frigate.data_processing.post.object_descriptions uses frigate.config.camera.camera, so a change to frigate.config.camera.camera can break frigate.data_processing.post.object_descriptions, while a change to frigate.data_processing.post.object_descriptions can't break frigate.config.camera.camera.

Position

Below the diagonal: frigate.data_processing.post.object_descriptions uses a module listed above it, which is the healthy direction.

31→20 frigate.data_processing.post.object_descriptions uses frigate.config.config✕

Connections

1 pair of types, where a type in frigate.data_processing.post.object_descriptions uses a type in frigate.config.config.

The types involved

• frigate.data_processing.post.object_descriptions.ObjectDescriptionProcessor → frigate.config.config.FrigateConfig

Direction

frigate.data_processing.post.object_descriptions uses frigate.config.config, so a change to frigate.config.config can break frigate.data_processing.post.object_descriptions, while a change to frigate.data_processing.post.object_descriptions can't break frigate.config.config.

Position

Below the diagonal: frigate.data_processing.post.object_descriptions uses a module listed above it, which is the healthy direction.

31→24 frigate.data_processing.post.object_descriptions uses frigate.data_processing.post.api✕

Connections

1 pair of types, where a type in frigate.data_processing.post.object_descriptions uses a type in frigate.data_processing.post.api.

The types involved

• frigate.data_processing.post.object_descriptions.ObjectDescriptionProcessor → frigate.data_processing.post.api.PostProcessorApi

Direction

frigate.data_processing.post.object_descriptions uses frigate.data_processing.post.api, so a change to frigate.data_processing.post.api can break frigate.data_processing.post.object_descriptions, while a change to frigate.data_processing.post.object_descriptions can't break frigate.data_processing.post.api.

Position

Below the diagonal: frigate.data_processing.post.object_descriptions uses a module listed above it, which is the healthy direction.

32→3 frigate.data_processing.post.review_descriptions uses frigate.comms.inter_process✕

Connections

1 pair of types, where a type in frigate.data_processing.post.review_descriptions uses a type in frigate.comms.inter_process.

The types involved

• frigate.data_processing.post.review_descriptions.ReviewDescriptionProcessor → frigate.comms.inter_process.InterProcessRequestor

Direction

frigate.data_processing.post.review_descriptions uses frigate.comms.inter_process, so a change to frigate.comms.inter_process can break frigate.data_processing.post.review_descriptions, while a change to frigate.data_processing.post.review_descriptions can't break frigate.comms.inter_process.

Position

Below the diagonal: frigate.data_processing.post.review_descriptions uses a module listed above it, which is the healthy direction.

32→6 frigate.data_processing.post.review_descriptions uses frigate.data_processing.types✕

Connections

2 pairs of types, where a type in frigate.data_processing.post.review_descriptions uses a type in frigate.data_processing.types.

The types involved

• frigate.data_processing.post.review_descriptions.ReviewDescriptionProcessor → frigate.data_processing.types.DataProcessorMetrics
• frigate.data_processing.post.review_descriptions.ReviewDescriptionProcessor → frigate.data_processing.types.PostProcessDataEnum

Direction

frigate.data_processing.post.review_descriptions uses frigate.data_processing.types, so a change to frigate.data_processing.types can break frigate.data_processing.post.review_descriptions, while a change to frigate.data_processing.post.review_descriptions can't break frigate.data_processing.types.

Position

Below the diagonal: frigate.data_processing.post.review_descriptions uses a module listed above it, which is the healthy direction.

32→19 frigate.data_processing.post.review_descriptions uses frigate.config.camera.camera✕

Connections

1 pair of types, where a type in frigate.data_processing.post.review_descriptions uses a type in frigate.config.camera.camera.

The types involved

• frigate.data_processing.post.review_descriptions.ReviewDescriptionProcessor → frigate.config.camera.camera.CameraConfig

Direction

frigate.data_processing.post.review_descriptions uses frigate.config.camera.camera, so a change to frigate.config.camera.camera can break frigate.data_processing.post.review_descriptions, while a change to frigate.data_processing.post.review_descriptions can't break frigate.config.camera.camera.

Position

Below the diagonal: frigate.data_processing.post.review_descriptions uses a module listed above it, which is the healthy direction.

32→20 frigate.data_processing.post.review_descriptions uses frigate.config.config✕

Connections

1 pair of types, where a type in frigate.data_processing.post.review_descriptions uses a type in frigate.config.config.

The types involved

• frigate.data_processing.post.review_descriptions.ReviewDescriptionProcessor → frigate.config.config.FrigateConfig

Direction

frigate.data_processing.post.review_descriptions uses frigate.config.config, so a change to frigate.config.config can break frigate.data_processing.post.review_descriptions, while a change to frigate.data_processing.post.review_descriptions can't break frigate.config.config.

Position

Below the diagonal: frigate.data_processing.post.review_descriptions uses a module listed above it, which is the healthy direction.

32→24 frigate.data_processing.post.review_descriptions uses frigate.data_processing.post.api✕

Connections

1 pair of types, where a type in frigate.data_processing.post.review_descriptions uses a type in frigate.data_processing.post.api.

The types involved

• frigate.data_processing.post.review_descriptions.ReviewDescriptionProcessor → frigate.data_processing.post.api.PostProcessorApi

Direction

frigate.data_processing.post.review_descriptions uses frigate.data_processing.post.api, so a change to frigate.data_processing.post.api can break frigate.data_processing.post.review_descriptions, while a change to frigate.data_processing.post.review_descriptions can't break frigate.data_processing.post.api.

Position

Below the diagonal: frigate.data_processing.post.review_descriptions uses a module listed above it, which is the healthy direction.

33→2 frigate.data_processing.post.semantic_trigger uses frigate.comms.event_metadata_updater✕

Connections

1 pair of types, where a type in frigate.data_processing.post.semantic_trigger uses a type in frigate.comms.event_metadata_updater.

The types involved

• frigate.data_processing.post.semantic_trigger.SemanticTriggerProcessor → frigate.comms.event_metadata_updater.EventMetadataPublisher

Direction

frigate.data_processing.post.semantic_trigger uses frigate.comms.event_metadata_updater, so a change to frigate.comms.event_metadata_updater can break frigate.data_processing.post.semantic_trigger, while a change to frigate.data_processing.post.semantic_trigger can't break frigate.comms.event_metadata_updater.

Position

Below the diagonal: frigate.data_processing.post.semantic_trigger uses a module listed above it, which is the healthy direction.

33→3 frigate.data_processing.post.semantic_trigger uses frigate.comms.inter_process✕

Connections

1 pair of types, where a type in frigate.data_processing.post.semantic_trigger uses a type in frigate.comms.inter_process.

The types involved

• frigate.data_processing.post.semantic_trigger.SemanticTriggerProcessor → frigate.comms.inter_process.InterProcessRequestor

Direction

frigate.data_processing.post.semantic_trigger uses frigate.comms.inter_process, so a change to frigate.comms.inter_process can break frigate.data_processing.post.semantic_trigger, while a change to frigate.data_processing.post.semantic_trigger can't break frigate.comms.inter_process.

Position

Below the diagonal: frigate.data_processing.post.semantic_trigger uses a module listed above it, which is the healthy direction.

33→6 frigate.data_processing.post.semantic_trigger uses frigate.data_processing.types✕

Connections

2 pairs of types, where a type in frigate.data_processing.post.semantic_trigger uses a type in frigate.data_processing.types.

The types involved

• frigate.data_processing.post.semantic_trigger.SemanticTriggerProcessor → frigate.data_processing.types.DataProcessorMetrics
• frigate.data_processing.post.semantic_trigger.SemanticTriggerProcessor → frigate.data_processing.types.PostProcessDataEnum

Direction

frigate.data_processing.post.semantic_trigger uses frigate.data_processing.types, so a change to frigate.data_processing.types can break frigate.data_processing.post.semantic_trigger, while a change to frigate.data_processing.post.semantic_trigger can't break frigate.data_processing.types.

Position

Below the diagonal: frigate.data_processing.post.semantic_trigger uses a module listed above it, which is the healthy direction.

33→20 frigate.data_processing.post.semantic_trigger uses frigate.config.config✕

Connections

1 pair of types, where a type in frigate.data_processing.post.semantic_trigger uses a type in frigate.config.config.

The types involved

• frigate.data_processing.post.semantic_trigger.SemanticTriggerProcessor → frigate.config.config.FrigateConfig

Direction

frigate.data_processing.post.semantic_trigger uses frigate.config.config, so a change to frigate.config.config can break frigate.data_processing.post.semantic_trigger, while a change to frigate.data_processing.post.semantic_trigger can't break frigate.config.config.

Position

Below the diagonal: frigate.data_processing.post.semantic_trigger uses a module listed above it, which is the healthy direction.

33→24 frigate.data_processing.post.semantic_trigger uses frigate.data_processing.post.api✕

Connections

1 pair of types, where a type in frigate.data_processing.post.semantic_trigger uses a type in frigate.data_processing.post.api.

The types involved

• frigate.data_processing.post.semantic_trigger.SemanticTriggerProcessor → frigate.data_processing.post.api.PostProcessorApi

Direction

frigate.data_processing.post.semantic_trigger uses frigate.data_processing.post.api, so a change to frigate.data_processing.post.api can break frigate.data_processing.post.semantic_trigger, while a change to frigate.data_processing.post.semantic_trigger can't break frigate.data_processing.post.api.

Position

Below the diagonal: frigate.data_processing.post.semantic_trigger uses a module listed above it, which is the healthy direction.

34→2 frigate.data_processing.real_time.custom_classification uses frigate.comms.event_metadata_updater✕

Connections

1 pair of types, where a type in frigate.data_processing.real_time.custom_classification uses a type in frigate.comms.event_metadata_updater.

The types involved

• frigate.data_processing.real_time.custom_classification.CustomObjectClassificationProcessor → frigate.comms.event_metadata_updater.EventMetadataPublisher

Direction

frigate.data_processing.real_time.custom_classification uses frigate.comms.event_metadata_updater, so a change to frigate.comms.event_metadata_updater can break frigate.data_processing.real_time.custom_classification, while a change to frigate.data_processing.real_time.custom_classification can't break frigate.comms.event_metadata_updater.

Position

Below the diagonal: frigate.data_processing.real_time.custom_classification uses a module listed above it, which is the healthy direction.

34→3 frigate.data_processing.real_time.custom_classification uses frigate.comms.inter_process✕

Connections

2 pairs of types, where a type in frigate.data_processing.real_time.custom_classification uses a type in frigate.comms.inter_process.

The types involved

• frigate.data_processing.real_time.custom_classification.CustomObjectClassificationProcessor → frigate.comms.inter_process.InterProcessRequestor
• frigate.data_processing.real_time.custom_classification.CustomStateClassificationProcessor → frigate.comms.inter_process.InterProcessRequestor

Direction

frigate.data_processing.real_time.custom_classification uses frigate.comms.inter_process, so a change to frigate.comms.inter_process can break frigate.data_processing.real_time.custom_classification, while a change to frigate.data_processing.real_time.custom_classification can't break frigate.comms.inter_process.

Position

Below the diagonal: frigate.data_processing.real_time.custom_classification uses a module listed above it, which is the healthy direction.

34→6 frigate.data_processing.real_time.custom_classification uses frigate.data_processing.types✕

Connections

2 pairs of types, where a type in frigate.data_processing.real_time.custom_classification uses a type in frigate.data_processing.types.

The types involved

• frigate.data_processing.real_time.custom_classification.CustomObjectClassificationProcessor → frigate.data_processing.types.DataProcessorMetrics
• frigate.data_processing.real_time.custom_classification.CustomStateClassificationProcessor → frigate.data_processing.types.DataProcessorMetrics

Direction

frigate.data_processing.real_time.custom_classification uses frigate.data_processing.types, so a change to frigate.data_processing.types can break frigate.data_processing.real_time.custom_classification, while a change to frigate.data_processing.real_time.custom_classification can't break frigate.data_processing.types.

Position

Below the diagonal: frigate.data_processing.real_time.custom_classification uses a module listed above it, which is the healthy direction.

34→17 frigate.data_processing.real_time.custom_classification uses frigate.config.classification✕

Connections

2 pairs of types, where a type in frigate.data_processing.real_time.custom_classification uses a type in frigate.config.classification.

The types involved

• frigate.data_processing.real_time.custom_classification.CustomObjectClassificationProcessor → frigate.config.classification.CustomClassificationConfig
• frigate.data_processing.real_time.custom_classification.CustomStateClassificationProcessor → frigate.config.classification.CustomClassificationConfig

Direction

frigate.data_processing.real_time.custom_classification uses frigate.config.classification, so a change to frigate.config.classification can break frigate.data_processing.real_time.custom_classification, while a change to frigate.data_processing.real_time.custom_classification can't break frigate.config.classification.

Position

Below the diagonal: frigate.data_processing.real_time.custom_classification uses a module listed above it, which is the healthy direction.

34→20 frigate.data_processing.real_time.custom_classification uses frigate.config.config✕

Connections

2 pairs of types, where a type in frigate.data_processing.real_time.custom_classification uses a type in frigate.config.config.

The types involved

• frigate.data_processing.real_time.custom_classification.CustomObjectClassificationProcessor → frigate.config.config.FrigateConfig
• frigate.data_processing.real_time.custom_classification.CustomStateClassificationProcessor → frigate.config.config.FrigateConfig

Direction

frigate.data_processing.real_time.custom_classification uses frigate.config.config, so a change to frigate.config.config can break frigate.data_processing.real_time.custom_classification, while a change to frigate.data_processing.real_time.custom_classification can't break frigate.config.config.

Position

Below the diagonal: frigate.data_processing.real_time.custom_classification uses a module listed above it, which is the healthy direction.

34→25 frigate.data_processing.real_time.custom_classification uses frigate.data_processing.real_time.api✕

Connections

2 pairs of types, where a type in frigate.data_processing.real_time.custom_classification uses a type in frigate.data_processing.real_time.api.

The types involved

• frigate.data_processing.real_time.custom_classification.CustomObjectClassificationProcessor → frigate.data_processing.real_time.api.DeferredRealtimeProcessorApi
• frigate.data_processing.real_time.custom_classification.CustomStateClassificationProcessor → frigate.data_processing.real_time.api.DeferredRealtimeProcessorApi

Direction

frigate.data_processing.real_time.custom_classification uses frigate.data_processing.real_time.api, so a change to frigate.data_processing.real_time.api can break frigate.data_processing.real_time.custom_classification, while a change to frigate.data_processing.real_time.custom_classification can't break frigate.data_processing.real_time.api.

Position

Below the diagonal: frigate.data_processing.real_time.custom_classification uses a module listed above it, which is the healthy direction.

35→2 frigate.data_processing.real_time.license_plate uses frigate.comms.event_metadata_updater✕

Connections

1 pair of types, where a type in frigate.data_processing.real_time.license_plate uses a type in frigate.comms.event_metadata_updater.

The types involved

• frigate.data_processing.real_time.license_plate.LicensePlateRealTimeProcessor → frigate.comms.event_metadata_updater.EventMetadataPublisher

Direction

frigate.data_processing.real_time.license_plate uses frigate.comms.event_metadata_updater, so a change to frigate.comms.event_metadata_updater can break frigate.data_processing.real_time.license_plate, while a change to frigate.data_processing.real_time.license_plate can't break frigate.comms.event_metadata_updater.

Position

Below the diagonal: frigate.data_processing.real_time.license_plate uses a module listed above it, which is the healthy direction.

35→3 frigate.data_processing.real_time.license_plate uses frigate.comms.inter_process✕

Connections

1 pair of types, where a type in frigate.data_processing.real_time.license_plate uses a type in frigate.comms.inter_process.

The types involved

• frigate.data_processing.real_time.license_plate.LicensePlateRealTimeProcessor → frigate.comms.inter_process.InterProcessRequestor

Direction

frigate.data_processing.real_time.license_plate uses frigate.comms.inter_process, so a change to frigate.comms.inter_process can break frigate.data_processing.real_time.license_plate, while a change to frigate.data_processing.real_time.license_plate can't break frigate.comms.inter_process.

Position

Below the diagonal: frigate.data_processing.real_time.license_plate uses a module listed above it, which is the healthy direction.

35→6 frigate.data_processing.real_time.license_plate uses frigate.data_processing.types✕

Connections

1 pair of types, where a type in frigate.data_processing.real_time.license_plate uses a type in frigate.data_processing.types.

The types involved

• frigate.data_processing.real_time.license_plate.LicensePlateRealTimeProcessor → frigate.data_processing.types.DataProcessorMetrics

Direction

frigate.data_processing.real_time.license_plate uses frigate.data_processing.types, so a change to frigate.data_processing.types can break frigate.data_processing.real_time.license_plate, while a change to frigate.data_processing.real_time.license_plate can't break frigate.data_processing.types.

Position

Below the diagonal: frigate.data_processing.real_time.license_plate uses a module listed above it, which is the healthy direction.

35→20 frigate.data_processing.real_time.license_plate uses frigate.config.config✕

Connections

1 pair of types, where a type in frigate.data_processing.real_time.license_plate uses a type in frigate.config.config.

The types involved

• frigate.data_processing.real_time.license_plate.LicensePlateRealTimeProcessor → frigate.config.config.FrigateConfig

Direction

frigate.data_processing.real_time.license_plate uses frigate.config.config, so a change to frigate.config.config can break frigate.data_processing.real_time.license_plate, while a change to frigate.data_processing.real_time.license_plate can't break frigate.config.config.

Position

Below the diagonal: frigate.data_processing.real_time.license_plate uses a module listed above it, which is the healthy direction.

35→23 frigate.data_processing.real_time.license_plate uses frigate.data_processing.common.license_plate.mixin✕

Connections

1 pair of types, where a type in frigate.data_processing.real_time.license_plate uses a type in frigate.data_processing.common.license_plate.mixin.

The types involved

• frigate.data_processing.real_time.license_plate.LicensePlateRealTimeProcessor → frigate.data_processing.common.license_plate.mixin.LicensePlateProcessingMixin

Direction

frigate.data_processing.real_time.license_plate uses frigate.data_processing.common.license_plate.mixin, so a change to frigate.data_processing.common.license_plate.mixin can break frigate.data_processing.real_time.license_plate, while a change to frigate.data_processing.real_time.license_plate can't break frigate.data_processing.common.license_plate.mixin.

Position

Below the diagonal: frigate.data_processing.real_time.license_plate uses a module listed above it, which is the healthy direction.

35→25 frigate.data_processing.real_time.license_plate uses frigate.data_processing.real_time.api✕

Connections

1 pair of types, where a type in frigate.data_processing.real_time.license_plate uses a type in frigate.data_processing.real_time.api.

The types involved

• frigate.data_processing.real_time.license_plate.LicensePlateRealTimeProcessor → frigate.data_processing.real_time.api.RealTimeProcessorApi

Direction

frigate.data_processing.real_time.license_plate uses frigate.data_processing.real_time.api, so a change to frigate.data_processing.real_time.api can break frigate.data_processing.real_time.license_plate, while a change to frigate.data_processing.real_time.license_plate can't break frigate.data_processing.real_time.api.

Position

Below the diagonal: frigate.data_processing.real_time.license_plate uses a module listed above it, which is the healthy direction.

36→1 frigate.ptz.autotrack uses frigate.camera✕

Connections

1 pair of types, where a type in frigate.ptz.autotrack uses a type in frigate.camera.

The types involved

• frigate.ptz.autotrack.PtzMotionEstimator → frigate.camera.PTZMetrics

Direction

frigate.ptz.autotrack uses frigate.camera, so a change to frigate.camera can break frigate.ptz.autotrack, while a change to frigate.ptz.autotrack can't break frigate.camera.

Position

Below the diagonal: frigate.ptz.autotrack uses a module listed above it, which is the healthy direction.

36→19 frigate.ptz.autotrack uses frigate.config.camera.camera✕

Connections

2 pairs of types, where a type in frigate.ptz.autotrack uses a type in frigate.config.camera.camera.

The types involved

• frigate.ptz.autotrack.PtzAutoTracker → frigate.config.camera.camera.CameraConfig
• frigate.ptz.autotrack.PtzMotionEstimator → frigate.config.camera.camera.CameraConfig

Direction

frigate.ptz.autotrack uses frigate.config.camera.camera, so a change to frigate.config.camera.camera can break frigate.ptz.autotrack, while a change to frigate.ptz.autotrack can't break frigate.config.camera.camera.

Position

Below the diagonal: frigate.ptz.autotrack uses a module listed above it, which is the healthy direction.

36→20 frigate.ptz.autotrack uses frigate.config.config✕

Connections

1 pair of types, where a type in frigate.ptz.autotrack uses a type in frigate.config.config.

The types involved

• frigate.ptz.autotrack.PtzAutoTracker → frigate.config.config.FrigateConfig

Direction

frigate.ptz.autotrack uses frigate.config.config, so a change to frigate.config.config can break frigate.ptz.autotrack, while a change to frigate.ptz.autotrack can't break frigate.config.config.

Position

Below the diagonal: frigate.ptz.autotrack uses a module listed above it, which is the healthy direction.

36→22 frigate.ptz.autotrack uses frigate.comms.dispatcher✕

Connections

1 pair of types, where a type in frigate.ptz.autotrack uses a type in frigate.comms.dispatcher.

The types involved

• frigate.ptz.autotrack.PtzAutoTracker → frigate.comms.dispatcher.Dispatcher

Direction

frigate.ptz.autotrack uses frigate.comms.dispatcher, so a change to frigate.comms.dispatcher can break frigate.ptz.autotrack, while a change to frigate.ptz.autotrack can't break frigate.comms.dispatcher.

Position

Below the diagonal: frigate.ptz.autotrack uses a module listed above it, which is the healthy direction.

36→28 frigate.ptz.autotrack uses frigate.track.tracked_object✕

Connections

1 pair of types, where a type in frigate.ptz.autotrack uses a type in frigate.track.tracked_object.

The types involved

• frigate.ptz.autotrack.PtzAutoTracker → frigate.track.tracked_object.TrackedObject

Direction

frigate.ptz.autotrack uses frigate.track.tracked_object, so a change to frigate.track.tracked_object can break frigate.ptz.autotrack, while a change to frigate.ptz.autotrack can't break frigate.track.tracked_object.

Position

Below the diagonal: frigate.ptz.autotrack uses a module listed above it, which is the healthy direction.

37→14 frigate.track uses frigate.config.camera.detect✕

Connections

1 pair of types, where a type in frigate.track uses a type in frigate.config.camera.detect.

The types involved

• frigate.track.ObjectTracker → frigate.config.camera.detect.DetectConfig

Direction

frigate.track uses frigate.config.camera.detect, so a change to frigate.config.camera.detect can break frigate.track, while a change to frigate.track can't break frigate.config.camera.detect.

Position

Below the diagonal: frigate.track uses a module listed above it, which is the healthy direction.

37→28 frigate.track uses frigate.track.tracked_object✕

Connections

1 pair of types, where a type in frigate.track uses a type in frigate.track.tracked_object.

The types involved

• frigate.track.tracked_object → frigate.track.tracked_object.TrackedObject

Direction

frigate.track uses frigate.track.tracked_object, so a change to frigate.track.tracked_object can break frigate.track, while a change to frigate.track can't break frigate.track.tracked_object.

Position

Below the diagonal: frigate.track uses a module listed above it, which is the healthy direction.

38→19 frigate.track.object_processing uses frigate.config.camera.camera✕

Connections

1 pair of types, where a type in frigate.track.object_processing uses a type in frigate.config.camera.camera.

The types involved

• frigate.track.object_processing.TrackedObjectProcessor → frigate.config.camera.camera.CameraConfig

Direction

frigate.track.object_processing uses frigate.config.camera.camera, so a change to frigate.config.camera.camera can break frigate.track.object_processing, while a change to frigate.track.object_processing can't break frigate.config.camera.camera.

Position

Below the diagonal: frigate.track.object_processing uses a module listed above it, which is the healthy direction.

38→20 frigate.track.object_processing uses frigate.config.config✕

Connections

1 pair of types, where a type in frigate.track.object_processing uses a type in frigate.config.config.

The types involved

• frigate.track.object_processing.TrackedObjectProcessor → frigate.config.config.FrigateConfig

Direction

frigate.track.object_processing uses frigate.config.config, so a change to frigate.config.config can break frigate.track.object_processing, while a change to frigate.track.object_processing can't break frigate.config.config.

Position

Below the diagonal: frigate.track.object_processing uses a module listed above it, which is the healthy direction.

38→22 frigate.track.object_processing uses frigate.comms.dispatcher✕

Connections

1 pair of types, where a type in frigate.track.object_processing uses a type in frigate.comms.dispatcher.

The types involved

• frigate.track.object_processing.TrackedObjectProcessor → frigate.comms.dispatcher.Dispatcher

Direction

frigate.track.object_processing uses frigate.comms.dispatcher, so a change to frigate.comms.dispatcher can break frigate.track.object_processing, while a change to frigate.track.object_processing can't break frigate.comms.dispatcher.

Position

Below the diagonal: frigate.track.object_processing uses a module listed above it, which is the healthy direction.

38→28 frigate.track.object_processing uses frigate.track.tracked_object✕

Connections

1 pair of types, where a type in frigate.track.object_processing uses a type in frigate.track.tracked_object.

The types involved

• frigate.track.object_processing.TrackedObjectProcessor → frigate.track.tracked_object.TrackedObject

Direction

frigate.track.object_processing uses frigate.track.tracked_object, so a change to frigate.track.tracked_object can break frigate.track.object_processing, while a change to frigate.track.object_processing can't break frigate.track.tracked_object.

Position

Below the diagonal: frigate.track.object_processing uses a module listed above it, which is the healthy direction.

38→36 frigate.track.object_processing uses frigate.ptz.autotrack✕

Connections

1 pair of types, where a type in frigate.track.object_processing uses a type in frigate.ptz.autotrack.

The types involved

• frigate.track.object_processing.TrackedObjectProcessor → frigate.ptz.autotrack.PtzAutoTracker

Direction

frigate.track.object_processing uses frigate.ptz.autotrack, so a change to frigate.ptz.autotrack can break frigate.track.object_processing, while a change to frigate.track.object_processing can't break frigate.ptz.autotrack.

Position

Below the diagonal: frigate.track.object_processing uses a module listed above it, which is the healthy direction.

39→1 frigate.video uses frigate.camera✕

Connections

2 pairs of types, where a type in frigate.video uses a type in frigate.camera.

The types involved

• frigate.video.detect → frigate.camera.CameraMetrics
• frigate.video.detect → frigate.camera.PTZMetrics

Direction

frigate.video uses frigate.camera, so a change to frigate.camera can break frigate.video, while a change to frigate.video can't break frigate.camera.

Position

Below the diagonal: frigate.video uses a module listed above it, which is the healthy direction.

39→3 frigate.video uses frigate.comms.inter_process✕

Connections

1 pair of types, where a type in frigate.video uses a type in frigate.comms.inter_process.

The types involved

• frigate.video.detect → frigate.comms.inter_process.InterProcessRequestor

Direction

frigate.video uses frigate.comms.inter_process, so a change to frigate.comms.inter_process can break frigate.video, while a change to frigate.video can't break frigate.comms.inter_process.

Position

Below the diagonal: frigate.video uses a module listed above it, which is the healthy direction.

39→7 frigate.video uses frigate.detectors.detector_config✕

Connections

1 pair of types, where a type in frigate.video uses a type in frigate.detectors.detector_config.

The types involved

• frigate.video.detect → frigate.detectors.detector_config.ModelConfig

Direction

frigate.video uses frigate.detectors.detector_config, so a change to frigate.detectors.detector_config can break frigate.video, while a change to frigate.video can't break frigate.detectors.detector_config.

Position

Below the diagonal: frigate.video uses a module listed above it, which is the healthy direction.

39→14 frigate.video uses frigate.config.camera.detect✕

Connections

1 pair of types, where a type in frigate.video uses a type in frigate.config.camera.detect.

The types involved

• frigate.video.detect → frigate.config.camera.detect.DetectConfig

Direction

frigate.video uses frigate.config.camera.detect, so a change to frigate.config.camera.detect can break frigate.video, while a change to frigate.video can't break frigate.config.camera.detect.

Position

Below the diagonal: frigate.video uses a module listed above it, which is the healthy direction.

39→19 frigate.video uses frigate.config.camera.camera✕

Connections

2 pairs of types, where a type in frigate.video uses a type in frigate.config.camera.camera.

The types involved

• frigate.video.detect → frigate.config.camera.camera.CameraConfig
• frigate.video.ffmpeg → frigate.config.camera.camera.CameraConfig

Direction

frigate.video uses frigate.config.camera.camera, so a change to frigate.config.camera.camera can break frigate.video, while a change to frigate.video can't break frigate.config.camera.camera.

Position

Below the diagonal: frigate.video uses a module listed above it, which is the healthy direction.

39→37 frigate.video uses frigate.track✕

Connections

1 pair of types, where a type in frigate.video uses a type in frigate.track.

The types involved

• frigate.video.detect → frigate.track.ObjectTracker

Direction

frigate.video uses frigate.track, so a change to frigate.track can break frigate.video, while a change to frigate.video can't break frigate.track.

Position

Below the diagonal: frigate.video uses a module listed above it, which is the healthy direction.

40→2 frigate.api uses frigate.comms.event_metadata_updater✕

Connections

1 pair of types, where a type in frigate.api uses a type in frigate.comms.event_metadata_updater.

The types involved

• frigate.api.fastapi_app → frigate.comms.event_metadata_updater.EventMetadataPublisher

Direction

frigate.api uses frigate.comms.event_metadata_updater, so a change to frigate.comms.event_metadata_updater can break frigate.api, while a change to frigate.api can't break frigate.comms.event_metadata_updater.

Position

Below the diagonal: frigate.api uses a module listed above it, which is the healthy direction.

40→5 frigate.api uses frigate.config.camera.updater✕

Connections

2 pairs of types, where a type in frigate.api uses a type in frigate.config.camera.updater.

The types involved

• frigate.api.config_util → frigate.config.camera.updater.CameraConfigUpdateEnum
• frigate.api.fastapi_app → frigate.config.camera.updater.CameraConfigUpdatePublisher

Direction

frigate.api uses frigate.config.camera.updater, so a change to frigate.config.camera.updater can break frigate.api, while a change to frigate.api can't break frigate.config.camera.updater.

Position

Below the diagonal: frigate.api uses a module listed above it, which is the healthy direction.

40→9 frigate.api uses frigate.models✕

Connections

4 pairs of types, where a type in frigate.api uses a type in frigate.models.

The types involved

• frigate.api.auth → frigate.models.User
• frigate.api.chat_util → frigate.models.Event
• frigate.api.export → frigate.models.Export
• frigate.api.export → frigate.models.ExportCase

Direction

frigate.api uses frigate.models, so a change to frigate.models can break frigate.api, while a change to frigate.api can't break frigate.models.

Position

Below the diagonal: frigate.api uses a module listed above it, which is the healthy direction.

40→20 frigate.api uses frigate.config.config✕

Connections

6 pairs of types, where a type in frigate.api uses a type in frigate.config.config.

The types involved

• frigate.api.app → frigate.config.config.FrigateConfig
• frigate.api.chat → frigate.config.config.FrigateConfig
• frigate.api.config_util → frigate.config.config.FrigateConfig
• frigate.api.fastapi_app → frigate.config.config.FrigateConfig
• frigate.api.media_auth → frigate.config.config.FrigateConfig
• frigate.api.motion_search → frigate.config.config.FrigateConfig

Direction

frigate.api uses frigate.config.config, so a change to frigate.config.config can break frigate.api, while a change to frigate.api can't break frigate.config.config.

Position

Below the diagonal: frigate.api uses a module listed above it, which is the healthy direction.

40→38 frigate.api uses frigate.track.object_processing✕

Connections

1 pair of types, where a type in frigate.api uses a type in frigate.track.object_processing.

The types involved

• frigate.api.media → frigate.track.object_processing.TrackedObjectProcessor

Direction

frigate.api uses frigate.track.object_processing, so a change to frigate.track.object_processing can break frigate.api, while a change to frigate.api can't break frigate.track.object_processing.

Position

Below the diagonal: frigate.api uses a module listed above it, which is the healthy direction.