Hey @eisfabian - thanks for all of your hard work here!
I've heard a couple of rumblings now that the 'sorted' mdoc files PACE writes out here
|
def writeMdoc(header, items, filename): |
|
content = "" |
|
for line in header: |
|
if line.startswith("[T"): |
|
content += os.linesep |
|
content += line + os.linesep |
|
content += os.linesep |
|
for i, item in enumerate(items): |
|
content += "[ZValue = " + str(i) + "]" + os.linesep |
|
item.pop("ZValue") |
|
item.pop("index") |
|
for key, attr in item.items(): |
|
content += key + " = " |
|
for val in attr: |
|
content += str(val) + " " |
|
content += os.linesep |
|
content += os.linesep |
|
with open(filename, "w", newline="") as f: |
|
f.write(content) |
|
return |
differ enough from SerialEM's files that Warp 2.0 fails to parse them correctly (e.g. warpem/warp#310)
I could write extra compatibility code but it might avoid other problems elsewhere to make the files here better match those produced by SerialEM, what do you think?
Hey @eisfabian - thanks for all of your hard work here!
I've heard a couple of rumblings now that the 'sorted' mdoc files PACE writes out here
PACEtomo/PACEtomo.py
Lines 261 to 280 in 90d5ad2
differ enough from SerialEM's files that Warp 2.0 fails to parse them correctly (e.g. warpem/warp#310)
I could write extra compatibility code but it might avoid other problems elsewhere to make the files here better match those produced by SerialEM, what do you think?