글

Design review in Omniverse Kit: change the design, get an AI answer in 0.1 s and GPU physics in 1.7 s

-
이미지
In short Omniverse Kit can be more than a viewer for generative-design results. Inside one Kit session I raised a flooded plant step by step. At each step a U-Net surrogate painted the flood on the USD stage in 125 ms, and NVIDIA Warp confirmed it on the GPU in the same session, in 1.7 s once its solver loop was replayed as a CUDA graph. Warp cleared the plant from +0.4 m; the U-Net, trained only on GA layouts, kept false alarms on the raised platform. That is the case for marking it unconfirmed . Across 115 what-if layouts it had never seen, the U-Net layer missed 1 of 58 real dangers . An untrained physics proxy shown just as fast missed 9. It raised more false alarms than the proxy (8 against 5), the cheaper kind of mistake while Warp confirms. Everything lives in OpenUSD: per-request values, a confirmed flag, 6,810 values read back with 0 mismatches. CUDA graphs cut a Warp run inside Kit from 59 s to 2.0 s. Synthetic site, assumed unit costs, no client data. This is the secon...
댓글 쓰기
Read more »

Cross-checking a GD loop against HEC-RAS 2D, inside one USD file

-
이미지
In short One cross-check of one plan proves little. I compared my GPU solver, NVIDIA Warp, with HEC-RAS 2D on all four plans that compete for the decision: the current plan, the GD-balanced plan, the GA optimum, and the optimum after repair. The danger verdicts agreed at all 56 facility aprons, so the loop's decision holds under the industry-standard solver too: after repair, the current plan A is the cheapest of the cross-checked plans with no danger (plan D, found later by the flood-aware GA, was not cross-checked). HEC-RAS was deeper at every apron, by 0.02–0.12 m on average per facility. Both results live in the same OpenUSD file and sit side by side in Omniverse Kit (280 values read back, 0 mismatches). If the AI training labels were shifted by the measured difference, 0.17 % of them would flip from safe to danger (at most 1.63 %). I did not re-score the surrogates. Why this matters for AI: in the extended GD–AI loop the simulation is the AI's teacher. Checking the solver...
댓글 쓰기
Read more »

Case 2: the cheapest road alignment, after the rain — and where my model ran out of resolution

-
이미지
In short I ran the same loop as the plant case on a road-alignment GD over synthetic terrain: generative design → simulation on what each design builds → OpenUSD and Omniverse Kit → AI measured against a baseline. The cost table changed the winner: once standard drainage is costed, the cheapest alignment moves from R00 to R03, with no simulation needed. The simulation, at 10 m, could not add anything decision-grade. It flipped the winner again by only 0.5 %, and not under every cost assumption, on a grid that cannot resolve ditches and culverts. I do not count that as a result. A re-run at 2.5 m (16 times the cells) on the GPU gave the same pattern, so it is still not a decision claim. AI gained nothing over the cheap baseline (0 of 3 splits); there was nothing to win. The method lesson: build the consequence geometry at the scale of the design element that controls the physics. Synthetic terrain, assumed unit costs, no client data. This is the second case for the method in the com...
댓글 쓰기
Read more »

Linking generative design to simulation in Omniverse: a method, and where else it applies

-
이미지
In short Rendering a generative-design (GD) result in Omniverse is easy. Making the simulation change the design decision is the hard part, and the part worth writing about. The method I settled on is one loop with three contracts: a decision criterion written down before running, a simulation run on the geometry each design would actually create, and an OpenUSD file that carries the design numbers, alternatives and simulation results together. It worked on a water-treatment-plant layout: the GA's "optimal" layout flooded on its own ground and lost its lead. Each NVIDIA tool carries one part: Warp on the GPU makes simulating every alternative routine, OpenUSD carries the contract, Omniverse Kit is the live review stage, and AI fills the wait where a person is waiting. It also extends the GD–AI Loop: the alternatives GD generates are built and simulated in a virtual site, and those results become the AI's training data. Below: the case-by-case images, the rules I wou...
댓글 쓰기
Read more »