Ashwin Bhat

@kwokcb Is there an example of a node with `__`? Do we need to place a restriction on node name specification or handle this in shader generation?

After switching to `HwTransmissionRenderMethod::TRANSMISSION_REFRACTION` the result might be acceptable, but we are missing transparency (alpha) 

I created a test case to demonstrate USD/HdSt workflow [here](https://github.com/autodesk-forks/MaterialX/commit/ab218c0e7eb51bc87a9601ac0d85480229a0352a) to highlight the issue. Input paths for both surface materials are identical though the generated shader code isn't. **Shader one...

I've added a catch benchmark to repro [here ](https://github.com/autodesk-forks/MaterialX/tree/bhata/shadergen_perf) Each sample loads about 20 documents, validates them and generates shader for them. When --benchmark-samples 10, we are loading 200 documents....

``` Similar test with 100 samples (2000 documents) GenShader: Scalabilty Check ------------------------------------------------------------------------------- benchmark name samples iterations estimated mean low mean high mean std dev low std dev high std dev...

Yes, I believe we could improve many workflows by defining the notion of a library document that is referred to for validation, shader generation, baking and other workflows. I think...

@jstone-lucasfilm I did a quick prototype by introducing an API to allow registering node library. This seems promising i.e. validation and shader generation seem be to ok. I have not...

Hey @bernardkwok Modifying the search logic to search Data library first and fallback to local sound reasonable. It will probably help with the embedded workflow, though I think we should...

Hi @rasmusbonnedal Can you confirm if this occurs if you explicitly set the target colorspace in the baking context using `context.getOptions().targetColorSpaceOverride = linrec_709` I'm wondering if this is because the...

I like this node concept and the agree with the motivation. It does help reduce the duplication. I'm curious if we could just extend `nodedef` to support multiple types so...