Commit 4ab2cfe2 authored by Mikaël Salson's avatar Mikaël Salson Committed by Vidjil Team
Browse files

server/.../models/{db,task}.py: Results can be hidden

We add a new field to the results_file stating that they can be hidden.
This means that those results shouldn't appear in the last processed
results. They should not be taken into consideration when fusing results.
They should not be proposed when comparing results.

A first example of those hidden results is when we launch a grep reads.
This is just a process launched behind the scene that should not be
made explicit to the user.

Fix #3899
parent ee7e0c6d
......@@ -209,6 +209,7 @@ db.define_table('results_file',
Field('config_id', 'reference config', ondelete='SET NULL'),
Field('scheduler_task_id', 'integer'),
Field('hidden', 'boolean', default = False, notnull = True),
Field('data_file', 'upload',
length=LENGTH_UPLOAD, autodelete=AUTODELETE))
......@@ -148,6 +148,7 @@ def schedule_run(id_sequence, id_config, grep_reads=None):
ts = time.time()
data_id = db.results_file.insert(sequence_file_id = id_sequence,
run_date = datetime.datetime.fromtimestamp(ts).strftime('%Y-%m-%d %H:%M:%S'),
hidden = grep_reads is not None,
config_id = id_config )
args = [id_sequence, id_config, data_id, grep_reads]
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment