You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two things I need to explain prior to explaining the issue:
The first jobs of the usual end-to-end OMR workflow look like this: The Fast Pixelwise job outputs images in a non-png format, so those images go through PNG jobs. The png images then go to the Convert to one-bit job, and those one-bit images go to the Despeckle job.
Each job in Rodan has a specific file type that it can receive as an input. As a consequence, a given job can only be connected to a job that can receive the file type it produces. If you try to connect two jobs that aren't compatible, Rodan just won't let you; the input port will stay red, and nothing you can do will connect those two jobs. For example, if I want to connect an output of the Fast Pixelwise job, you can see that I can connect it to the PNG job, but I can't connect it directly to the Convert to one-bit job.
Trying.to.connect.Fast.Pixelwise.mov
Ok! So the issue is this: when you add the Column splitting job to an end-to-end OMR workflow, it goes between the Fast Pixelwise job and the three PNG jobs at the top of each column. @yinanazhou has informed me that the Column splitting job converts images both to png and to one-bit. So technically, it should be possible to remove the PNG and Convert to one-bit jobs from the workflow and connect the Column splitting job directly to the Despeckle jobs. Right? WRONG. For some reason, the Despeckle jobs refuse to be connected to the Column splitting outputs. It looks like Despeckle will only accept inputs from three jobs: Convert to one-bit, Despeckle, and Dilate.
It's absolutely possible to add Column splitting to the OMR workflow without removing the redundant jobs. I don't yet know if that redundancy is a problem or not. But it certainly adds to the confusion! I'm not sure whether the solution should be:
Remove the conversion to png and one-bit from the Column splitting job;
Allow Despeckle to receive inputs from Column splitting.
All thoughts welcome!
The text was updated successfully, but these errors were encountered:
There are two things I need to explain prior to explaining the issue:
The first jobs of the usual end-to-end OMR workflow look like this:
The
Fast Pixelwise
job outputs images in a non-png format, so those images go throughPNG
jobs. The png images then go to theConvert to one-bit
job, and those one-bit images go to theDespeckle
job.Each job in Rodan has a specific file type that it can receive as an input. As a consequence, a given job can only be connected to a job that can receive the file type it produces. If you try to connect two jobs that aren't compatible, Rodan just won't let you; the input port will stay red, and nothing you can do will connect those two jobs. For example, if I want to connect an output of the
Fast Pixelwise
job, you can see that I can connect it to thePNG
job, but I can't connect it directly to theConvert to one-bit
job.Trying.to.connect.Fast.Pixelwise.mov
Ok! So the issue is this: when you add the
Column splitting
job to an end-to-end OMR workflow, it goes between theFast Pixelwise
job and the threePNG
jobs at the top of each column. @yinanazhou has informed me that theColumn splitting
job converts images both to png and to one-bit. So technically, it should be possible to remove thePNG
andConvert to one-bit
jobs from the workflow and connect theColumn splitting
job directly to theDespeckle
jobs. Right? WRONG. For some reason, theDespeckle
jobs refuse to be connected to theColumn splitting
outputs. It looks likeDespeckle
will only accept inputs from three jobs:Convert to one-bit
,Despeckle
, andDilate
.It's absolutely possible to add
Column splitting
to the OMR workflow without removing the redundant jobs. I don't yet know if that redundancy is a problem or not. But it certainly adds to the confusion! I'm not sure whether the solution should be:Column splitting
job;Despeckle
to receive inputs fromColumn splitting
.All thoughts welcome!
The text was updated successfully, but these errors were encountered: