-
Notifications
You must be signed in to change notification settings - Fork 48
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
feat: provide createWebWorker #1033
feat: provide createWebWorker #1033
Conversation
Re: #1018 |
fd5abbf
to
fa30f9c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool. A step to removing this benign error causing "tee up" of a pipeline in VolView:
https://github.com/Kitware/VolView/blob/main/src/io/dicom.ts#L69-L79
To "prime the pump" for the .wasm
asset, should VolView just fetch()
its custom .wasm file? Is there another possible speedup by asking the browser to "load" the .wasm?
const outputs = null | ||
const inputs = null | ||
const stdoutStderrPath = 'stdout-stderr-test' | ||
const { returnValue, stdout, stderr } = await itk.runPipeline(webWorker, stdoutStderrPath, args, outputs, inputs, { pipelineWorkerUrl }) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is { pipelineWorkerUrl }
option still needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope! Good catch.
I made a note to investigate this more in #1018 |
So compatible web workers can be created explicitly when desired.
fa30f9c
to
923726e
Compare
b52eab7
into
InsightSoftwareConsortium:main
So compatible web workers can be created explicitly when desired.