mirror of
https://github.com/nerfstudio-project/nerfstudio.git
synced 2026-11-15 04:13:57 +08:00
Ethan Weberandevonneng
7e9a56fac4
* starting docs for pipelines * working on an example * clearing output * starting to implement config changes and add documentation * wip: removed cicular imports; porting basic config into python; todo: get python setups workin * circular imports again * wip: pausing at dataloader sort of working * break for today * running vanilla * wip need to get all the config docs working * laptop about to die * instant ngp working * added all configs for all methods; not tested yet: [mipnerf360, nerfw, semantic_nerf] * unpacking later * done with pylinting * mostly done. just need to do docs and one test * added import order to docs * fixing near/far plane and other config things * making loggers also instantiable via configs * docs * lint * making --help work with dcargs * moving configs back into flat * convert list to tuples; fixed post init function with mutable params * lint * made run_eval and benchmarking scripts compatible with new config/dcargs * lint * added option to load configs from presaved config Co-authored-by: evonneng <evonne_ng@berkeley.edu>
Python Kernel and Client Viewer App communication
The purpose of this document is to explain how to communicate from Python with the Client Viewer app. We will eventually move this into the read the docs.
- Python Kernel (nerfactory code)
- Bridge Server
- Client Viewer App
We have two types of components that we want to keep state updated in both locations.
- Widgets
- The widgets are used to keep track of the
- SceneNode
- The scene nodes are used to represent the three.js objects. The properties relevant to these objects are the following:
"object", "transform", "properties".
- The scene nodes are used to represent the three.js objects. The properties relevant to these objects are the following:
Checklist
-
Currently using request-reply (REQ, REP with zmq). I.e., Python Kernel -> Bridge Server <-> Client Viewer App. We want a way to update the Python Kernel when the Bridge Server is updated. This requries some form of binding with callbacks. When the Bridge Server is updated, we want to update the binded Python variable. We can take inspiration from ipywidgets.