Patrik Gyltefors

gyltefors

About Me

Expertise
Not Specified
Location
Not Specified
Website

Connect

Recent Forum Posts

Work Item Indices April 28, 2019, 12:29 a.m.

kenxu
there are some general issues with the JSON/CSV nodes that kept popping up for different use cases, so having those ironed out while TOPs is still in early development would be very nice. Also, for standalone PDG, I expect users will start to pipe in a lot of different kinds of data, so having a basic set of flexible data retrieval nodes would likely become even more important.

Could not agree more. It's a repeated exercise at this point of looking at use cases that we may still not be addressing well, ironing out the wrinkles there, rinse and repeat. If you're open to it, we'd be up for a periodic call to see where the remaining issues are for you and see what we could do about it. Please message me in case you're interested.

I tried out the last stable release, and it totally broke my TOPs setup. I am going back to an old release for now, and will contact you directly regarding the various issues with these nodes.

Work Item Indices April 23, 2019, 1:23 a.m.

jason_iversen
In my opinion for complex cases it's (arguably) simpler to write the loader yourself. There is only so much you can expect from an UI interface such a format which can return such hugely varying data topology.

Learning Python is next on my list. I first learned HAPI, and wrote my pipeline using that. Hearing about TOPs, it seemed to be a better long term solution, so I am switching over to that. While I will eventually need to write some custom integration using Python, there are some general issues with the JSON/CSV nodes that kept popping up for different use cases, so having those ironed out while TOPs is still in early development would be very nice. Also, for standalone PDG, I expect users will start to pipe in a lot of different kinds of data, so having a basic set of flexible data retrieval nodes would likely become even more important.

Work Item Indices April 20, 2019, 1:01 a.m.

Again, another issue with CSV output. Handle multiple values Add Columns with a 2D position attribute gives:

position position1 position1 position1 and so on

The JSON/CSV related nodes are, honestly speaking, totally utterly broken. They have been for weeks. And it have kept me frustrated with TOPs for weeks. And it has prevented any kind of progress in my project for… WEEKS. Please, please, do something about these nodes. I can't believe how they can have been shipped with so many bugs! Did anyone ever use these for anything even resembling a real project???