BeebBenjamin / ansible.meshroom

Ansible deployment to provision a Linux virtual machine (VM) with a meshroom pipeline
0 stars 0 forks source link

Implementation Plan #1

Open BeebBenjamin opened 4 years ago

BeebBenjamin commented 4 years ago

I think we should use ansible as the base for this project because this can be used to provision a service on a local machine or a remote server, hence the name ansible.meshroom. Let me know if you can think of a better name later!

I envision this as being something that can use an API to upload pictures to and run some automated processes using meshroom, then dump the project files to a mounted storage drive so that people can do some manual checking/rework in blender before the service continues onto texturing after detecting changes in the files. We can create separate repos to hold some of the other code for the service once we know what we're dealing with.

This way OpenScan and PalaeoPi can offer a cloud processing option with our products, and other users can also set up their own for their own projects.

At this stage, this is open to change, these are just my ideas.

BeebBenjamin commented 4 years ago

There is an existing node.js pipline line the Smithsonian uses called The Cook may be good for ideas on implementation. I like the use of RESTful APIs to handle jobs and recipes for the pipeline. Something that I did not previously consider is also post processing e.g. mesh decimation, uv-mapping, normal-mapping, diffuse-mapping etc. It might be useful to make a list of the rough steps required and identify software that can do these via CL interface.

BeebBenjamin commented 4 years ago

Proposed Pipeline

Example Tasklist