<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><blockquote type="cite" class="">Because I would like to be able to perform existence/location tests on the client for CMB v4.</blockquote><br class=""></div><div class="">Ah, that’s a very good reason! I’ve cc’d Robert because he’s the guy to ask, but I can give you my version of an answer.</div><div class=""><br class=""></div><div class="">smtk::mesh currently supports two “interfaces”: Moab and Json. The Moab interface is the one that runs on the server, has the database, and does all of the actual work. The Json interface runs on the client, and it nulls out the database calls and only carries metainformation about mesh collections, mesh sets, etc. It looks as though these two are kept in sync somewhere in SaveJson, but the code is rather squirrely (maybe try SaveJSON::forManagerMeshes? The mesh info gets updated if JSON_MESHES is one of the flags passed to SaveJSON::forManager). Hope this helps!</div><div class=""><br class=""></div><div class="">Sincerely,</div><div class="">T.J.</div><br class=""><div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Thomas J. Corona, Ph.D.<br class="">Kitware, Inc.<br class="">Senior R&D Engineer<br class="">21 Corporate Drive<br class="">Clifton Park, NY 12065-8662<br class="">Phone: 518-881-4443</div></div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On May 12, 2017, at 1:19 PM, David Thompson <<a href="mailto:david.thompson@kitware.com" class="">david.thompson@kitware.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi TJ,<br class=""><br class=""><blockquote type="cite" class="">Just curious: why do you want to store the collection’s URL in the operator result? A collection holds its read and write locations, and you are free to change the collection’s write location (I think you automatically do so when you write a collection to disk).<br class=""></blockquote><br class="">Because I would like to be able to perform existence/location tests on the client for CMB v4. There is not a way for operator views to do a trial run of an operation on the server without triggering the result-handling stuff which prevents the "save smtk model" operator from running on the server. If the client and server have a different mesh manager, then the collections must have different FileLocation information. I was under the impression that the mesh manager tracked collections and meshsets on the client but did so without copying actual mesh data. Is that not so?<br class=""><br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Thanks,<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>David</div></div></blockquote></div><br class=""></body></html>