Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue when force enqueuing a measurement #153

Open
lcontami opened this issue Jun 29, 2018 · 8 comments
Open

Issue when force enqueuing a measurement #153

lcontami opened this issue Jun 29, 2018 · 8 comments

Comments

@lcontami
Copy link
Member

When force enqueuing, even if everything runs smoothly afterwards the Save task doesn't save data.
(this can be tested by, for example, raising an error in the checks of an instrument that doesn't affect the measurement run)

@MatthieuDartiailh
Copy link
Member

This may be moved to hqc_legacy if it affects only SaveTask. At one point, the checks method was promised to be called before perform but actually this is not true. Any initialization that MUST be run before perform should be run in prepare.

@MatthieuDartiailh
Copy link
Member

I cannot reproduce using a simple example (see below). Could you send me a config file ?

name = M
id = 001
[root_task]
    dep_type = exopy.task
    task_id = exopy.ComplexTask
    stoppable = True
    parallel = {}
    wait = {}
    access_exs = {}
    default_path = D:/Coding/Temp
    should_profile = False
    [[children_0]]
        dep_type = exopy.task
        task_id = exopy.LoopTask
        name = Akasaki
        stoppable = True
        parallel = {}
        wait = {}
        access_exs = {}
        timing = False
        [[[interface]]]
            dep_type = exopy.tasks.interface
            interface_id = exopy.LoopTask:exopy.IterableLoopInterface
            iterable = range(10)
        [[[children_0]]]
            dep_type = exopy.task
            task_id = exopy_hqc_legacy.SaveTask
            name = Gennes
            stoppable = True
            parallel = {}
            wait = {'activated': True}
            access_exs = {}
            saving_target = File
            folder = {default_path}
            filename = test.dat
            header = Test
            array_size = ""
            saved_values = "[('item0', '{Akasaki_index}')]"
    [[children_1]]
        dep_type = exopy.task
        task_id = exopy.FormulaTask
        name = Dirac
        stoppable = True
        parallel = {}
        wait = {'activated': True}
        access_exs = {}
        formulas = "[('item0', '*+')]"
[monitors]
    [[exopy.text_monitor]]
        rule_0 = Measurement entries
        rule_1 = Loop progress
        rule_2 = Instrument ids
        displayed = "['root/Akasaki_progress', 'root/meas_time', 'root/Akasaki_value', 'root/Dirac_item0']"
        undisplayed = "['root/default_path', 'root/meas_name', 'root/meas_id', 'root/meas_date']"
        hidden = "['root/Akasaki_point_number', 'root/Akasaki_index']"
[pre_hooks]
    [[exopy.internal_checks]]
[post_hooks]

@lcontami
Copy link
Member Author

lcontami commented Jul 9, 2018

I got this error when enqueuing multiple times measurement with an acquisition card (and stupid checks in the acquisition card driver):

2018-06-28_sweep_gbisdir_cav_011.zip

@MatthieuDartiailh
Copy link
Member

What am I supposed to see in this file, it looks like a regular datafile to me ? Could I get the .ini and the corrupted datafile (I would like to know what part of it was missing: the whole file, the header, data, just some raws ....)

@lcontami
Copy link
Member Author

lcontami commented Jul 10, 2018

Zut. Here is the ini file
sweep_gbisdir_cav_011.meas.ini.zip

The whole datafile is missing. However the log file is generated:
sweep_gbisdir_cav_012-main2018-06-28_0.log

@MatthieuDartiailh
Copy link
Member

Could you also send to me the application of this particular run (it may help me understand the issue with the card) ?

@lcontami
Copy link
Member Author

What do you mean by application? Exopy version? The use I have for this measurement?
It is just a vsd-vg 2D map with a current+cavity measurement.

I enqueued a first measure and started it with no issue. However when enquiring a second one while the card was being used, the checks failed (as reported in another issue) and I force enqueued.

@MatthieuDartiailh
Copy link
Member

Sorry I meant the application log of this particular run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants