Jump to content

Recommended Posts

14 hours ago, drjdpowell said:

I’m recording my work on Messenger Library and all other reuse libraries, and hope to claim at least some of them also.   JSON just happens to be what I am working on right now.  

Yes. But what is the requirement that means it has to be under your company name? Is it that you fear if it is not then your argument to the tax office is diminished or is there a specific clause that states open source does not constitute a "product" that you own and therefore cannot be accepted? i.e. is this a speculative move or is there a definite clause that applies?

Link to post
Share on other sites
  • Replies 240
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

The easiest way by far is to use the [un]Flatten to XML primitives, which can take objects and variants as arguments, and convert the XML to/from JSON. with simple regex/search/replace. Why they didn'

View File JSON LabVIEW JSON is a data interchange format (sometimes compared to XML, but simpler). There are multiple projects to create a JSON package for LabVIEW. T

I tried to use this tool. And it looks great, however the function 'Variant to JSON' fails with a variant inside an object. I made the following changes: -Added support for Variant. By using 'Unwrap

Posted Images

Speculative, to establish that the work is legitimate R&D of my company.  I want to be able to show a tax inspector a company-branded product on the LabVIEW Tools Network.

BTW, I’ve found I can separate the new stuff into a separate, non-conflicting project, so LAVA JSON can be left as is (I’ll bring out a new version with some modest performance improvements).

Link to post
Share on other sites
5 minutes ago, drjdpowell said:

Speculative, to establish that the work is legitimate R&D of my company.  I want to be able to show a tax inspector a company-branded product on the LabVIEW Tools Network.

BTW, I’ve found I can separate the new stuff into a separate, non-conflicting project, so LAVA JSON can be left as is (I’ll bring out a new version with some modest performance improvements).

Just be careful they don't label you a contractor then there are zero benefits to being a company apart from liability.

Link to post
Share on other sites
  • 1 month later...

Hi all,

I am trying to start working with this library, but it doesn't look straight forward to me. There are only 2 polymorphic VIs that I can access to, but I see that you guys are using a wide variety of VIs that I cannot even get to find. Is there any "user guide" thread in the forum that I am missing? Can you guys address me or give me some hints on how to start with the library?

Thank you so much. 

Link to post
Share on other sites
12 hours ago, JPina said:

Hi all,

I am trying to start working with this library, but it doesn't look straight forward to me. There are only 2 polymorphic VIs that I can access to, but I see that you guys are using a wide variety of VIs that I cannot even get to find. Is there any "user guide" thread in the forum that I am missing? Can you guys address me or give me some hints on how to start with the library?

Thank you so much. 

Place the polymorphic VI on the diagram and click the label at the bottom. A menu with all the functions will appear which will enable you to choose from all the functions. Copy and paste the VI (or drag with the mouse+CTRL to create a copy) and choose another function as before to create another function.

  • Like 1
Link to post
Share on other sites
  • 9 months later...

Could you reattach with the control values saved as default?

-------------------------------------------------------------------------------------------------------------------

 noi that o to  |   do choi o to  |  do choi xe hoi 
 
 
Edited by Jan_bee
edit content
Link to post
Share on other sites
  • 5 months later...

Hi,

is there any reason why the VIs ar not reentrant? (shared clone) If there is no reason, could someone modify the VIs to reentrant and update the package.

The reason i would like reentrancy is that when using this library in parallel loops, they wait for each other.

BR Ziga 

Link to post
Share on other sites

I was going to say I don’t do blanket shared-reentrant, as that create at least one copy per processor, and for lesser-used functions this is memory overhead that is often not justified.  However, I’m not sure that is true of LabVIEW 2017 (seems to be only one clone).  

Edited by drjdpowell
Link to post
Share on other sites
  • 5 months later...

I'm using JSON to store control and indicator values of which I don't know the datatype.

I use dynamic VI calling, I set controls using VI Reference -> Set Control values, run the VI, and get the indicators using 'Get Control values'; those need an give back variants. These values I want to load from JSON and store back to JSON

Link to post
Share on other sites
  • 10 months later...

I'm using this library, but I've had to modify alot of the variant related attributes for performance and data handling.  Most of what I have removes the OpenG stuff and directly casts types.  It will also properly preserve data names/typing unlike the current version without extra variant to data casts.

I don't really want to go through all the data types that I'm not using, but If you're still interested in maintaining this its probably a worthwhile upgrade.

Get as Variant

image.png.254f1005fbc7d6444708d8aad8bf8d5c.png

image.png.1b5f272306b67eba59faa6fa5d89b7b4.png

logic will change to look more like this

image.png.6acfa92607afb9b74ba1caf6d0a8677f.png

 

surely there will be some difficulties with this approach on certain data types, and I dont really want to go through and test them, but dynamically building variants is pretty slow and some of the functions are quarter baked which removes the type string.

I've got an assortment of scalars, arrays, and clusters working with this method.

Let me know if you're interested in this.

Link to post
Share on other sites

I ask about performance because I wouldn't have thought your new method would in general be faster.  

When I was considering how to improve the performance of this library I became convinced that I should produce a new package that delt directly with strings, abandoning the objects and variant attributes used here.  That package is JSONtext, which I use in all new work.  So I am unlikely to make more than minor improvements to this library.  However, someone else could continue development of LAVA JSON if they like.

 

Link to post
Share on other sites
  • 11 months later...

Hi,

I am using jsontext library and am wondering if circular reference is supported.  For example: I would like to get the value (10) when I ask for NeedValueFromAbove,

Here is a simple json file to illustrate my point

{

"Hello":

{

"World":10

},

"NeedValueFromAbove":{"$ref":"#/Hello/World"}

}

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By drjdpowell
      View File JSONtext
      Package for working with JSON.  Uses high-speed text parsing, rather than building an intermediate representation as with prior LabVIEW JSON libraries (this is much faster).  Allows easy working with "subitems" in JSON format, or one can convert to/from LabVIEW types.  Uses the new "malleable VIs" of LabVIEW 2017 to convert to any LabVIEW type directly.
      JSON text makes use of a form a JSON Path notation, allowing easy and rapid access to the subitems of interest.
      Requires LabVIEW 2017 and install by VIPM 2017 or later.
      Original conversation about JSONtext.
      On the LabVIEW Tools Network.
      JDP Science Tools group on NI.com.
      Copyright 2017 JDP Science Limited
      Submitter drjdpowell Submitted 08/02/2017 Category General LabVIEW Version 2017 License Type BSD (Most common)  
    • By drjdpowell
      Package for working with JSON.  Uses high-speed text parsing, rather than building an intermediate representation as with prior LabVIEW JSON libraries (this is much faster).  Allows easy working with "subitems" in JSON format, or one can convert to/from LabVIEW types.  Uses the new "malleable VIs" of LabVIEW 2017 to convert to any LabVIEW type directly.
      JSON text makes use of a form a JSON Path notation, allowing easy and rapid access to the subitems of interest.
      Requires LabVIEW 2017 and install by VIPM 2017 or later.
      Original conversation about JSONtext.
      On the LabVIEW Tools Network.
      JDP Science Tools group on NI.com.
      Copyright 2017 JDP Science Limited
    • By ThomasGutzler
      Hi,
      I'm receiving a JSON string from a web API, which I'm trying to convert into a cluster (of clusters) but I've run into some problems:
      1) Sometimes the order of the elements in the JSON string changes, which causes my conversion to fail.
      2) Sometimes the "object" returned via JSON is null, which causes my conversion to fail if I use clusters within clusters. It works with variants in clusters but then I need to convert the all the variants manually
      Is there any way to improve my code to fix those problems? The attached snippet is a simplified version. In my project, the first JSON string to data is done in a library. The second conversion from "result" variant to data is done in my application. This makes a direct conversion from JSON string more difficult.

    • By drjdpowell
      JSON is a data interchange format (sometimes compared to XML, but simpler). There are multiple projects to create a JSON package for LabVIEW. This is yet another one motivated by this hijacked conversation originally about a different project to convert JSON into LabVIEW Variants.

      This project uses a set of LVOOP classes to match the recursive structure of JSON, rather than variants. It allows conversation to and from JSON. All functionality is available through two polymorphic VIs: Set and Get. In addition to Get and Set VIs for common data types, one can also convert directly to or from complex clusters via variant-JSON tools.

      Copyright 2012-2016 James David Powell, Shaun Rumbell, Ton Plomp and James McNally.
      [Note: if you are using LabVIEW 2017, please also see the JSONtext library as a an alternative.]
    • By Pavanb
      Hi There 
      I want to go from TestStand's output i.e. database to HTML5 SPC charts. Sorta like http://moderndata.plot.ly/using-plotly-from-labview-via-python/ Has anyone done this or used Bokeh or Enthough's data tool before?  What about these tools with TDMS or HDF5?
      Thanks. I appreciate it.
      Best,
      Pavan 
      By the way, https://www.enthought.com/services/consulting/case-studies/TAIPAN/ (like TestStand without TestStand)
       



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.