-
Notifications
You must be signed in to change notification settings - Fork 0
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
#8: Adapt input and output to use compressed JSON format #106
#8: Adapt input and output to use compressed JSON format #106
Conversation
bf90fe6
to
b651602
Compare
|
a187dc8
to
4bd910e
Compare
…ean up OpenMP preprocessing
6da8f58
to
0f6c187
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems to be ok for input part as the unit test PASSED.
@cwschilly I have just one question: I am not sure about what output
means in the issue description because I don't see anything about output in the PR. There is some JSONGenerator class but it does not seem to be related to that issue
@tlamonthezie This issue is from over a year ago; my guess is that when it was opened, we thought that vt-tv might use a JSON writer. However, at least at the moment, we never write out JSON, so I don't think there's any work to be done for output |
Fixes #8
This changes vttv so that we read in every file in the input data directory. This means that there can't be extra files in there (for example, both compressed and un-compressed versions of the input data).
Also reworks OpenMP preprocessing, since the changes to JSON reading affected the
omp parallel for
inparse_render.cc
.