Difference in trace.json format

[cchrysostomou]

I am currently running synthego-open/ice using the latest docker (I didn't want to explicitly use latest tag): synthego/ice:fix_throwing_out_wildtype_hdr. However, it looks as though the structure of the trace.json file differs from the structure of the trace.json file on your website. For example, when running a batch analysis using the docker version, the trace.json file looks as follows:
{
'ctrl_sample': {'trace_data': [], 'cutsite': #, 'guide_start': #, 'guide_end': #., 'pam_start': #, 'pam_end': #},
'edited_sample': {'trace_data': [], 'cutsite': #}
}

But when I run the same batch on your website and ask for the results back, the format looks as follows:
[
{
'ctrl_sample': {'trace_data': [], 'guide_target': {}, 'cutsites': [{}]}
'edited_sample': {'trace_data': [], 'cutsites': [{}]}
}
]

Am I doing something wrong to not recreate the same trace.json file? This is potentially problematic for me when trying to analyze multiplexed samples where the trace.json should be returned as a list with multiple cut sites.

[hsiaut]

Hi Constantine,
You should try running the latest github master repo rather than the Docker image. The Docker image is not quite up to date.

[cchrysostomou]

I just ran the program using both pip install synthego_ice and using the latest github master repo. In both of those instances the trace file json format do not match the web-based tool version. As previously, they are a set of keys rather than list of keys for each multiplex item.