Currently three.js does not support loading of STEP or Parasolid files. These files will need to be converted to something like "STL" which does have an available three.js loader. I'm thinking that right now the best solution will be to have the user "attach" their .step or parasolid file to the form, then provide a button which will.

1. upload the file to the controller
2. convert the file
3. download the converted file, and
4. display to the user

Questions:

• How do we convert the file on the system side?
  • One option is do the conversion via Blender, which appears to be possible via simple command line arguments
  • If we don't want to employ another dependency, it looks like Salome can be used to convert these files to stl. The process is a little more complicated though and will involve the creation of a python file to handle the conversion. I've found some examples here.
• How do we persist the converted data?
  • Maybe just attach it to the form and save it in the json store?
  • Do what we do in myjobs and create a staged directly immediately? This is actually more involved than that because we would need a place to store the file before the workflow is created if we want to do that.
  • A combination of both?
• How do we reconcile the current state, where a geometry is defined in advance, with one where the geometry can be defined by the user. What is the error workflow for bad uploads?

The version of paperclip used here contains a security vulnerability as reported by github. This should be updated to a newer version.

We found a potential security vulnerability in one of your dependencies.

The paperclip dependency defined in Gemfile.lock has a known high severity security vulnerability in version range >= 3.1.4, <= 5.1.0 and should be updated.