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
Issue 4387 gl tf extras #4571
Issue 4387 gl tf extras #4571
Conversation
@Brijendra21 A description of your changes would be helpful. Also I'm pretty sure you can clean up the diff significantly. It seems some files are marked deleted instead of rename + couple of changes. Currently with 1 million lines added it's extremely hard to see what's going on |
@Brijendra21 Thanks for adding the additional info. I am seeing some build errors on the CI. You can click the links and check the errors. Here's a little snippet of some build errors (below). Check jenkins for full logs.
Also, to @jmarrec point. Could you explain a bit on each of the wrapper classes that you've implemented. It would be good to know how this functionality works so we can better maintain this going forward. I'd like to capture this and include it in our developer wiki docs. |
@Brijendra21 The thing that bothers me with the excess diff is that I want to ensure it can't be avoided (perhaps it cannot). It seems a bunch of files were renamed and maybe slightly modified, but git is registering that as a full file deletion and one file addition. For eg, what's the difference between RefBldgOutPatientNew2004_Chicago.gltf (former) and Sample_DOE-RefBldgOutPatientNew2004_Chicago.gltf (new) ? |
CI Results for c68e5db:
|
@jmarrec Yes we can avoid few of them if we decide to keep it in some other repository as a benchmark from the time of implementation. These are exported glTF files from various Tests and they rendered fine with 0 validation issues. |
@tijcolem These Wrapper Classes are only introduced as they're hiding the tinyglt::value as extras which is present in respective implementation of the same as Structure or Classes in Forward Translation Class and they serve the purpose of inferring the UserData Collection and MetaData against a loaded glTF model. |
Looks good to me! Let's get this merged so users can begin exporting and viewing the data attributes on glTF. |
This is an absolute minimal fix to have the tests passing, but really a refactor is warranted. The wrappers classes and superfluous, there's a lot of static storage objects throughout that should be deleting. The data layouts of the classes in GltfForwardTranslator makes little sense to me (using a tuple<string, T> makes little sense to me). cf #4571
This is an absolute minimal fix to have the tests passing, but I think we should refactor: * avoid all static storage objects * change the data layout and API in the classes that are in GltfForwardTranslator * just use `T` (eg double) instead of std::tuple<std::string, tinygltf::Value(T)> * provide a protected toGltfValue that will create the std::map<std::string, tinygltf::Value> * Move those to separate files (like the wrappers are) * Remove the wrappers (which are superflous now)The wrappers classes and superfluous, there's a lot of static storage objects throughout that should be deleting. The data layouts of the classes in GltfForwardTranslator makes little sense to me (using a tuple<string, T> makes little sense to me). cf #4571
Addition of Metadata and Userdata in the translated glTF
Pull Request Author
src/model/test
)src/energyplus/Test
)src/osversion/VersionTranslator.cpp
)Labels:
IDDChange
APIChange
Pull Request - Ready for CI
so that CI builds your PRReview Checklist
This will not be exhaustively relevant to every PR.