sintel-dev/sintel

sintel's Issues

Suggest minor changes to the current DB Schema

Event (the current version)

Each one of the anomalies detected by the pipelines is stored as an Event, which
contains the details about the start time, the stop time and the severity score.

Fields

• _id (ObjectID): Unique Identifier of this Event object
• signalrun_id (ObjectID - Foreign Key): Unique Identifier of the Signalrun during which this
  Event was detected.
• signal_id (ObjectID - Foreign Key): Unique Identifier of the Signal to which this Event relates
• start_time (Integer): Timestamp where the anomalous interval starts
• stop_time (Integer): Timestamp where the anomalous interval ends
• severity (Float): Severity score given by the pipeline to this Event
• source (String): ORION, SHAPE_MATCHING, or MANUALLY_CREATED
• num_annotations (int): Number of Annotation associated to this Event.
• insert_time (DateTime): Time when this Event Object was inserted

Event (the suggested version)

The previous version is not user friendly to read or track the latest tag information.

Fields

• _id (ObjectID): Unique Identifier of this Event object
• signalrun_id (ObjectID - Foreign Key): Unique Identifier of the Signalrun during which this
  Event was detected.
• signal_id (ObjectID - Foreign Key): Unique Identifier of the Signal to which this Event relates
• start_time (Integer): Timestamp where the anomalous interval starts
• stop_time (Integer): Timestamp where the anomalous interval ends
• severity (Float): Severity score given by the pipeline to this Event
• source (String): ORION, SHAPE_MATCHING, or MANUALLY_CREATED
• num_annotations (int): Number of Annotation associated to this Event.
• latest_tag (ObjectID - Foreign Key): Unique Identifier of the most recent Annotation with tag.
• insert_time (DateTime): Time when this Event Object was inserted

Event Interaction (the current version)

The Event Interaction collection records all the interaction history related to events.

Fields

• _id (ObjectID): Unique Identifier of this Interaction object
• event_id (ObjectID): Unique Identifier of the Event to which this event relates
• action (String): Action type performed on this event, such as delete, split, and adjust
• start_time (Integer): Timestamp where the anomalous interval starts
• stop_time (Integer): Timestamp where the anomalous interval ends
• created_by (String): Identifier of the user who interacted with the target Object
• insert_time (DateTime): Time when this Event Interaction Object was inserted

Event Interaction (the suggested version)

The previous version is not good for maintaining histories of annotations. Annotation can be created, deleted, or updated. So the interaction also needs to maintain this history.

Fields

• _id (ObjectID): Unique Identifier of this Interaction object
• event_id (ObjectID): Unique Identifier of the Event to which this event relates
• action (String): Action type performed on this event, such as delete, split, merge, adjust, and annotate (tag || comment)
• start_time (Integer): Timestamp where the anomalous interval starts
• stop_time (Integer): Timestamp where the anomalous interval ends
• annotation (ObjectID - Foreign Key): Unique Identifier of the newly created Annotation from this interaction action.
• created_by (String): Identifier of the user who interacted with the target Object
• insert_time (DateTime): Time when this Event Interaction Object was inserted

Download of demo dataset fails

• Sintel version: 0.1.0.dev0
• Python version: 3.8.17
• MongoDB version: 4.0 (defined in docker-compose-db.yml)
• Operating System: Ubuntu 20.04.6 LTS

Description

Download of demo dataset fails.
Has the URL for the demo dataset distribution location changed?

What I Did

$ make docker-db-up
rm -f -r ./db-instance/data/*
rm -f -r ./db-instance/log/*
mkdir -p db-instance
# this folder is for saving the downloaded demo mongodb data
mkdir -p db-instance/data
# this folder is for saving the log files
mkdir -p db-instance/log
# this folder is for saving the newly dumped mongodb data
mkdir -p db-instance/dump
curl -o sintel.tar.bz2 "https://d3-ai-sintel.s3.us-east-2.amazonaws.com/sintel.tar.bz2"
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   302    0   302    0     0    284      0 --:--:--  0:00:01 --:--:--   284
tar -xf sintel.tar.bz2 -C ./db-instance/data/ && rm sintel.tar.bz2
tar: This does not look like a tar archive
bzip2: (stdin) is not a bzip2 file.
tar: Child returned status 2
tar: Error is not recoverable: exiting now
make: *** [Makefile:78: docker-db-up] Error 2

For reference, the results of opening the URL of the demo dataset in a browser are shown below.

<Error>
  <Code>NoSuchBucket</Code>
  <Message>The specified bucket does not exist</Message>
  <BucketName>d3-ai-sintel</BucketName>
  <RequestId>BBDT03YZJZ8PH84F</RequestId>
  <HostId>V3ANwcCBC6xlySIw6V/mhrRmjGjr3TIuM84+oApwVKLwxz5rG4dN9NBaW3J1e1BEZDBr4vj+b2g=</HostId>
</Error>

the status of signalrun is not correctly save when failed

Description

When a signalrun is failed, the status of the signalrun will be not correctly saved.

See the error message below:

AttributeError: 'Signalrun' object has no attribute 'STATUS_ERROR'

Solution

Update

status = self.STATUS_ERROR

to

status = self.STATUS_ERRORED

Support HTTPS

To use public google oauth 2.0, sintel should update flask to support https.