Datasets:

---

EssentialAI

/

eai-taxonomy-code-w-dclm-100b-sample

like 2

Follow

Essential AI 409

ERROR: type should be string, got "https://project-haystack.org/forum/topic/feed Project Haystack Forum 2017-10-17T18:11:10Z Brian Frank https://project-haystack.org/forum/topic/551#0 Haystack Type System WG 2017-10-17T18:11:10Z\n\nOverview\n\nHaystack is designed around the concept of tagging entities with name/value pairs to describe facts about those entities. The formal definitions of these tags and their value types are captured in a machine readable format (Trio files) which is used to generate the tags section of this website. But how tags are combined lacks formal machine readable definitions. For example the description and constraints of how to model site/equip/point entities is largely described by documentation without a corresponding formal schema and machine readable format. Historically this has been by design since formalization of \"compound types\" introduces significant complexity. But with broader adaptation of Haystack, there seems to be a pent-up demand to formalize types/schema. We believe its time to tackle this problem, and would like to kick start a new working group.\n\nI have spent several weeks designing various prototypes with help from Matthew Giannini. By way of this post, I will describe a fairly complete prototype which serves as a starting point for a proposal on how types might work in Haystack. The prototype defines most of the Haystack model using a type system I will discuss here. I have made the source code and the documentation it generates available for download (discussed below).\n\nRequirements\n\nLeverage Markers: we wish to leverage Haystack's existing and extensive use of markers as the basis for a more advanced data type system. We do not wish to introduce a new concept such as a \"type\" tag.\n\nNo Indirection: all data semantics should be captured in the entity's tags. You should not be required to have previous knowledge (such as a data dictionary) or make an additional network request to infer semantics. For example if a point currently uses discharge air temp sensor, then that will not be coalesced into some abstract \"tag set\" name that requires another request to know that all those tags were applied. Or put another way: entities will always continue to expand their full set of tags inline.\n\nTooling: a common use case for a more advanced type system is to allow tool manufactures to develop UIs that \"guide\" users to properly tag their data. Capturing tag relationships and rules in machine format is a key requirement for tooling\n\nValidation: a machine readable schema allows validation of data models. But we acknowledge that type systems require a trade-off; more complex type systems are required to more fully validate data. And no declarative type system can perform 100% validation. We wish to strike a compromise with a practical type system that performs basic validation, but will not provide perfect validation.\n\nRDF: it is desired that enhancements to Haystack allow our taxonomy to be expressed in alternate formats such as RDFS, RDFa, micro-data, JSON-LD, etc. These technologies are based on the concept of subject-predicate-object triples that map well to Haystack's entity name/value tags. And ideally we want to map Haystack types to the RDF Schema class model.\n\nSource Definitions: the goal of this effort is to rewrite the project-haystack.org specification source material using the new definitions and formats as the authoritative source. The machine readable formats will be directly accessible over HTTP and also used to auto-generation the HTML presented on the site.\n\nObservations\n\nLets begin with a couple observations of how the existing model works. There are essentially only four \"root\" entity types: sites, equips, points, and weather stations. All other Haystack tags are used to annotate these four core entity types with additional information.\n\nThere are three distinct ways we use tags to annotate the core entity types:\n\n • Has Tags: an entity may have specific value based tags. For example a site entity may apply the area tag to define the building's square footage. This sort of tag usage includes all the tags which are neither markers nor refs.\n • Subtyping Tags: we use marker tags to create subtypes to further refine the semantics of a given entity. For example adding sensor to a point entity narrows the type of point represented\n • Relationship Tags: we use ref tags to establish relationships between entities. For example adding equipRef on a point defines a equip/point containment relationship\n\nIn all three cases, what we really desire is to document the behavior of a specific combination of tags. This has been a pain point maintaining the documentation. For example lets take the water tag. It has a generic definition which means \"associated with liquid water\". But it also has more specific definitions when paired with point, meter, or tank. In our final solution, we want tags to be defined generically with more specific documentation as we combine tags.\n\nTag Based Subtyping\n\nWe add marker tags to an entity to indicate a more specific type of the entity. For example we add ahu to equip to mark the equipment as an air handler unit. We can further mark the AHU with steamHeat to indicate its an AHU using steam from a central plant for heating. Each time we apply a marker tag we further restrict what the entity type represents. From a type system perspective, this is a form of subtyping.\n\nThere are two key observations to be made about how marker tags are used for subtyping:\n\n • Subtypes are often defined as an exclusive choice: for example an AHU can have hotWaterHeat, steamHeat, elecHeat, or gasHeat\n • Subtyping is multi-dimensional: for example I can subtype a AHU by its heating method, cooling method, and ductwork configuration (all simultaneously)\n\nThis pattern plays out in the documentation quite often in a non-formal way:\n\n • Point qualifier: sensor, cmd, sp\n • Point subject: air, water, steam, elec, etc\n • Point quantity: temp, flow, pressure, power, energy, etc\n • Power Qualifier: active, reactive, apparent\n • AHU heating: steamHeat, hotWaterHeat, gasHeat, elecHeat\n • AHU cooling: dxCool, chilledWaterCool\n • AHU ductwork: singleDuct, dualDuct, tripleDuct\n • VAV airflow: series, parallel\n • Chiller type: absorption, reciprocal, screw, centrifugal\n\nAnother important consideration is that these exclusive choices are often open ended. This is opposed to an enum in a programming language which is closed (once defined you may not add new choices to the enumeration). But in a data model type system, these enumerated choices may be expanded after the fact. An example might be a project which requires a subtype choice not covered by the standard Haystack tag library.\n\nType Names\n\nOne of the common questions I've heard over the years is this: why not just define a shorthand name for a combination of tags such as \"discharge air temp point\". But what would this name be? Creating a shortcut such as \"DAT\" would go against the principle of avoiding indirection to understand an entity's tags. And to provide the same information without indirection would lead to a name such as \"DischargeAirTempPoint\" which sort of defeats the purpose of creating new names. I would propose that any new synthetic name generated for Haystack's type system is strictly just a combination of existing tag names. For example the type that represents an AHU with steam heating:\n\nequip ahu steamHeat // tags separated by space\nequip-ahu-steamHeat // tags separated with dash\nequip+ahu+steamHeat // tags separated with plus\nsteamHeat ahu equip // most specific to least specific\n\nFor this proposal I will use the first option: a type name is a list of tags separated by space and ordered from least to most specific. For the prototype documentation HTML pages I used dash instead of space as a more URL friendly file name.\n\nSide note: I also investigated using camel case to join tags name together (if all tags were lowercase). But we have many tags such as hotWaterHeat where this would cause a problem. These compound tag names are a potential problem which could possibly be solved more elegantly through the type system. But I'll leave that as a discussion for the working group.\n\nNotation\n\nIn order to discuss how we might apply a type system to Haystack tags using the concepts above, we need some notation. I'm going to introduce a notation/syntax which I have found concise and readable to develop the prototype. However, my proposal is based on the abstraction concepts, not the specific syntax I am using here. However at some point we will need to formalize one or more machine readable formats which capture the type system abstractions.\n\nHere is the quick summary of notation:\n\ntype > tag // type has tag\ntype dim> // type has subtype dimension\ntype dim> tag // subtype choice within given dimension\ntype <ref> type // relationship definition\n\nLets look at each of these notations in more detail...\n\nNotation: Has\n\nLets start off with an entity which might have data tags:\n\nsite > area // Square footage of the site\nsite > tz // Timezone of the site\nsite > primaryFunction // Primary function of the site\nsite > yearBuilt // Original construction year of the site\n\nHere we using the syntax \"type > tag\" to define that the LHS (left hand side) type may optionally use the RHS (right hand side) tag according the definition given in the slash-slash comment. This definition is context specific to when the tag is applied to the LHS type.\n\nWe can use Python style indentation to omit the base type. The following has exactly the same semantics as the definitions above:\n\nsite \n > area // Square footage of the site\n > tz // Timezone of the site\n > primaryFunction // Primary function of the site\n > yearBuilt // Original construction year\n\nNotation: Subtype\n\nHere is how to define a subtype dimension\n\npoint subject> // Subject or substance of the point's measurement or control\npoint subject> air // Point related to air\npoint subject> water // Point related to water\npoint subject> steam // Point related to steam\npoint subject> elec // Point related to electricity\n\nHere we define a named dimension of subtyping on points. In this case the dimension name is subject as defined with the syntax \"type dim>\". Then we can define exclusive subtype choices for that dimension with the syntax \"type dim> tag\". Each choice defines a new type. In our example above, we have now defined the new types \"point air\", \"point water\", etc.\n\nWe can use indentation to collapse the definition above. And lets flush out more point subtypes to see how it works in practice:\n\npoint\n\nqualifier> // Classifies the point as a sensor, command, or setpoint\n sensor // Point is a sensor, input, AI/BI\n cmd // Point is a command, actuator, AO/BO\n sp // Point is a setpoint, soft point, internal control variable, schedule\n\nsubject> // Subject or substance of the point's measurement or control\n air // Point related to air\n water // Point related to water\n steam // Point related to steam\n elec // Point related to electricity\n refrig // Point related to refrigerant substance\n\nair\n\n quantity> // Quantity of air measured or controlled\n temp // Point related to dry bulb air temperature\n humidity // Point related to percent relative humidity of air\n flow // Point related to volumetric air flow\n pressure // Point related to static air pressure\n\nwater\n\n quantity> // Quantity of water measured or controlled\n temp // Point related to water temperature\n flow // Point related to volumetric water flow\n pressure // Point related to water pressure\n\n waterType> // Type of the water and its usage\n domestic // Tap water for drinking, washing, cooking, and flushing of toliets\n hot // Hot water used for heating or supply to hot taps\n chilled // Water used for cooling\n condenser // Water used used to remove heat through condensation\n makeup // Water used used to makeup water loss through leaks, evaporation, or blowdown\n blowdown // Water expelled from a system to remove mineral build up\n\nWhat is created as you define these dimensions and their choices is a \"type tree\" or \"decision tree\". Each time you add a marker tag it potentially opens up new choices to narrow the type along multiple branches (dimensions).\n\nNotation: Relationship\n\nLastly we need a notation to define relationships. Here are some examples:\n\nequip <equipRef> equip // Equipment contains sub-equipment\nequip <equipRef> point // Equipment contains point\n\nA relationship has a LHS type and a RHS type and one or more relationship tags grouped between the \"<>\". The first relationship tag must be a ref tag which is applied to the entity on the RHS to reference the LHS. Or put another way the RHS is the \"from entity\" and the LHS is the \"to entity\" in terms of the ref tag. Lets deconstruct this example:\n\nLHS Tags RHS Doc definition of relationship\n----- --------- ----- -------------------------------\nequip <equipRef> point // Equipment contains point\n\nThe LHS type is any entity tagged with the equip marker tag. The RHS is a point entity. In order to apply the relationship, then the equipRef tag must applied to the RHS (the point) and reference the LHS (the equip). When all of those conditions hold true, then the relationship applies.\n\nWe can define additional tags to apply to the RHS entity for more complex relationships:\n\nequip ahu <equipRef discharge> point air // AHU point associated with discharge air duct\nequip ahu <equipRef return> point air // AHU point associated with return air duct\n\nIn the example above, the LHS (to) is AHU equipment and the RHS (from) is points associated with the measurement/control of air. The relationship tags include both a ref tag as well as a \"section tag\" to apply to the point to create the specified relationship. This model allows us to reuse the subtype definition of \"point air\" without duplicating massive point tag combinations under each equipment (like we do today).\n\nHere are some more relationship examples for a steam plant:\n\nequip plant steam\n\n <steamPlantRef> equip ahu steamHeat // Plant supplies steam to AHU for heating \n <equipRef> equip boiler // Plant contains boiler\n <equipRef leaving> point steam // Point associated with steam leaving plant as heating supply\n <equipRef delta> point steam // Point associated with steam differential between leaving and entering\n <equipRef entering> point steam // Point associated with steam returning to plant to be heated back up\n\nPrototype\n\nI have developed a complete prototype for the type system discussed above. This is actually my third prototype (the first two being dead ends). The prototype is developed in Fantom and has following key features:\n\n • TagDef: models a single tag definition\n • TypeDef: models type, its has tags, dimensions, and relationships\n • Model: immutable data structure for all the TagDef and TypeDef\n • Loader: loads one or more haydef text files to build an in-memory model\n • DocGen: generates simple HTML documentation for a model\n • lib/*.haydef: definitions for about 70% of the Haystack model using notation discussed\n\nYou can download the prototype include source code, definitions, and example documentation from:\n\nhttps://project-haystack.org/download/build/haystack-model-prototype-2017-10-17.zip\n\nTo run the documentation use this command which generates HTML files to \"./doc/\"\n\nbin/fan haystackModel::DocGen\n\nThe prototype has quite a bit of the model flushed out including\n\n • air, water, steam points\n • electrical meters and power/energy/volt/current points\n • central plants (using simple, not existing compound tags)\n • chillers\n • boilers\n • VAVs\n\nNone of it is complete, but its pretty far along to test out the concepts. If you are interested in this topic, then I would encourage you to download it and at least look thru the haydef text files.\n\nNext Steps\n\nThere seems to lots of momentum with various organizations, vendors, and community members around this core problem. I believe now is a great time to tackle the problem head on. So I'd like to create a new working group (WG) for those interested. I'm thinking of a WG process with weekly webcast calls. Also feel free to post ideas/comments to the forum. If you are interested please use the \"Join Group\" command to join the WG.\n\nTerry Herr https://project-haystack.org/forum/topic/548#12 auto-tagging 2017-10-16T21:20:55Z\n\nGabe,\n\nthose are good articles. I found them a while back. That conference looks interesting. I am not aware that Johnson published anything regarding their standard. We have lots of BAS data sets, and many are Johnson. The standard I am referring to is typically only the last acronym in the longer point name which as you note also includes network controllers acronyms.\n\nChristian, LON was much better than BACnet at defining and requiring standard snvt's (point) naming https://www.lonmark.org/technical_resources/resource_files/snvt.pdf\n\nI believe BACnet is adopting equipment profiles and standard naming, which will make this problem less important some years down the road. In the meantime we are stuck with thousands of buildings with non standard point names.\n\nStephen Frank https://project-haystack.org/forum/topic/536#5 Maintaining consisting on points with Multiple Tags 2017-10-16T15:04:48Z\n\nI recently was sent this academic paper which has some great discussion of some of these issues:\n\nBrick: Towards a Unified Metadata Schema For Buildings\n\nIt builds on both Haystack and RDF and explicitly addresses some of the areas of weakness in Haystack right now, include sets of tags and a formal ontology.\n\nAlthough it seems pretty academic to me (and maybe clunky to implement, if those SPARQL queries are any indication), there are some good ideas in here that could likely be used alongside Haystack or else pulled into Haystack at some future point.\n\nChristian Tremblay https://project-haystack.org/forum/topic/548#11 auto-tagging 2017-10-16T02:58:58Z\n\n@Terry, I don't work a lot with Lonworks anymore but I remember their variables names being the same for standard applications like VFD or VAV...\n\nGabe Fierro https://project-haystack.org/forum/topic/548#10 auto-tagging 2017-10-14T12:31:21Z\n\nHi all:\n\nI'm a PhD student at UC Berkeley working on building metadata, analytics and controls. Just wanted to jump in and provide some pointers to some of the academic work in this area:\n\nDeconstructing human-readable tags\n\nIdentifying sensor streams\n\nThe BuildSys conference is a growing community of computer scientists, building scientists, mechanical/civil engineers, etc interested in these kinds of topics, so you can search past programs to find other related work.\n\nThe systems I linked above aren't \"production ready\", but they do offer promising avenues of being able to automatically extract tags from existing metadata and timeseries data. Terry, you mentioned that JCI has something like a standard for these point names. Is this written down/published anywhere that I could take a look? In the buildings I've worked with, there's been very little standardization around point names beyond common idiomatic abbreviations such as VAV and AHU. Point names usually betray more about the BMS network than they do about the actual physical relationships (such as which chiller connects to this AHU)\n\nTerry Herr https://project-haystack.org/forum/topic/548#9 auto-tagging 2017-10-13T11:37:33Z\n\nChristian & Aaron,\n\nWhat you describing is a good start - an every growing look-up library/dictionary of standard point names from OEM equipment vendors, and BAS vendors with the appropriate tags added. In our experience OEM vendors do have point name standards, but only Johnson Controls has anything approximating a standard. Most other BAS products allowed the tech-on-the-bucket to create his own point names. The latter case is where you need more sophisticated algorithms using more than just the point name to decipher.\n\nProject Haystack is great example of the community working together for collective benefit. The tagging standard is great, now we need to reduce the time and cost to apply them to a data set. I have seen an example of one tool and heard of another that can ingest (auto-discover) a BAS, apply tags, and then the appropriate rules/algorithms automatically apply. I am sure this will always require some human oversight /vetting, but it would be minimal.\n\nAaron Sanchez https://project-haystack.org/forum/topic/548#8 auto-tagging 2017-10-12T19:17:05Z\n\nThat's a great idea in theory. If we had a csv file for each vendor's point naming structure so that anyone using a system where auto-tagging was possible, they can pull the appopriate csv file. Also, if there were new point names there weren't on the list, anyone can add to each respective csv file and push so that it is up to date. I'm a fan of this idea.\n\nChristian Tremblay https://project-haystack.org/forum/topic/548#7 auto-tagging 2017-10-12T18:48:27Z\n\nAs we can see, there are a lot of solution allowing to tag automatically points. As a community though, would it be viable that some kind of \"sharing\" be possible for basic auto-tagging ?\n\nI'm wearing my integrator hat here. If I have some kind of CSV file (that can be used or modified to be used by any tool) with tags that I would just need to review, what a time saver.\n\nI'm pretty sure everyone is doing its own list actually.\n\nI would see something like :\n\njohnson_control_standard_variables.csv (DA-T : temp, sensor, air, discharge; etc...) ABB_drive_tags.csv CompanyX_HeatPump.csv\n\nFor this I work with variable names has those are typically standard for manufactured products...\n\nThis would not prevent the integrator to \"validate and verify\" that the tagging has been done correctly, but this certainly be valuable information.\n\nA versionning system like github would be very cool to handle those files and anyone could participate doing pull requests.\n\nAaron Sanchez https://project-haystack.org/forum/topic/548#6 auto-tagging 2017-10-12T18:13:56Z\n\nTerry,\n\nEverything you're describing is possible with FIN|Stack, we've just never created the tool ourselves. However, our Fin Framework, allows any user to build virtually anything they want on top of what's already built within FIN|Stack. Obviously you'll have to know axon to do some of these things but we've made it easier for people to launch tools for their functions with the Form Builder 2.0 documentation page.\n\nRicky Villa Valle https://project-haystack.org/forum/topic/550#1 Dropping points into nHaystack Service View results in all controller points showing under Hierarchy 2017-10-10T17:38:16Z\n\nHi Kyle,\n\nThe video are you viewing was made at the end of 2013, which by then an older version of the nhaystack module was being used. It has now changed and usually the haystack slot is used for tagging and specifying an equip if something else other than what its currently under.\n\nIn the newer version, it is automatically displaying all the points under a certain equip whether they have the haystack slot or not. Unfortunately there isn't a property that I know of that will display only the points that haystack slot.\n\nHowever, I do know that in FIN Stack, we have a property on the connector that allows you to toggle it. Then when dragging the entire site over, it would only bring over points with the haystack slot. Otherwise, it would bring in all points.\n\nHopefully Richard, or one of the others will be able to better answer your question. I would consider it a feature request on the Niagara side.\n\nKyle Herbst https://project-haystack.org/forum/topic/550#0 Dropping points into nHaystack Service View results in all controller points showing under Hierarchy 2017-10-10T11:54:39Z\n\nSorry for the lengthy title.\n\nUsing nHaystack 2.0.1 on a N4 4.2.36.34 system.\n\nTrying to click and drag points from my Networks and dropping them into my Site-Equip-Point Hierarchy page, as described on this video How-To created by J2\n\nhttps://www.youtube.com/watch?v=dStqInuDkiE\n\nOnce I create a Site/then Equip, I can drag one single point into the \"Drag Components here to add a haystack slot\" and the whole point list will populate underneath that associated equipment in the haystack window.\n\nThe only single point I've clicked an dragged over will appear with the haystack slot, as is should, however my import function gets messy as it will end up pulling all my points from that equipment (even ones that don't have a haystack tag) into Skyspark.\n\nIs there anything I'm doing wrong that's not being covered in that video? It seems to me that video was created in AX, not N4...however the process appears to be the same from what I can determine.\n\nLong story short, I'm trying to see if I can only have my Hierarchy display points that I want to drag and drop to add the haystack tag, rather than all points underneath that controller.\n\nThanks\n\nTerry Herr https://project-haystack.org/forum/topic/548#5 auto-tagging 2017-10-10T10:44:11Z\n\nThere are a number of tools that can apply tag values from an internal library, via pattern extraction from regular expression text search of the point name.\n\nBetter tools will take advantage of more than than the point name. Most bacnet drivers / discover tools can also extract - point type, units, description, present value,etc from the controller. And these can be used to help decipher / understand the point and add tags.\n\nThe best tools will also use historical time series data, machine learning methods, and an ever expanding dictionary as it learns from more and more data sets. The ideal is a tool that can completely and fully tag a data set without human involvement.\n\nMachine learning methods like - multi layer feature extraction, support vector machine, logistic regression, latent semantic indexing..\n\nThere are a number of researchers from DOE labs, UofC Berkely and Davis, that have done some fundamental research in the development of such a tool. We have one tool that was developed by United Technology Research Center and DOE funded that is a reasonable start, but needs completing. The tool is written in python.\n\nGreg Ingram https://project-haystack.org/forum/topic/545#5 Examples of TagKinds in JSON, Zinc and CSV format 2017-10-09T21:14:46Z\n\nCorrect, I'm working on a few connection APIs. I plan to post a link to them once I feel they are up to par during testing.\n\nI look forward to the test server once released.\n\nThx\n\nBrian Frank https://project-haystack.org/forum/topic/539#2 Two-speed Fans 2017-10-09T12:59:03Z\n\nIf its just one point, then I'd probably use an enum point:\n\npoint\nkind:\"Str\"\nenum:\"off,slow,fast\"\nBrian Frank https://project-haystack.org/forum/topic/545#4 Examples of TagKinds in JSON, Zinc and CSV format 2017-10-09T12:57:09Z\n\nIt sounds like maybe you are implementing your own client and/or server? In that case I think probably the best option might be to use one of the open source projects as a reference. For example the Java Haystack toolkit has a pretty extensive test suite including Zinc, JSON, etc tests. It also has a complete test server you can run and perform all those queries against (read, sub, unsub, etc). Or if you are working with a specific vendor use an actual project. Plus we are probably going to make this site itself a test server pretty soon\n\nGreg Ingram https://project-haystack.org/forum/topic/545#3 Examples of TagKinds in JSON, Zinc and CSV format 2017-10-09T00:24:24Z\n\nJust wanted to ping again to see if anyone had some examples. For example, do you have a large Zinc versus CSV versus JSON file with data similar to what is shown on https://project-haystack.org/doc/Csv?\n\nThanks in advance.\n\nRav Panchalingam https://project-haystack.org/forum/topic/403#11 nhaystack for Niagara 4 available 2017-10-06T05:28:03Z\n\nhello, is there any docs on how to write to a schedule object (via haystack API) ?\n\nAaron Sanchez https://project-haystack.org/forum/topic/548#4 auto-tagging 2017-10-05T19:13:51Z\n\nIf the tool works based off the names of the points. We, at J2 Innovations, have created a tool for this to work with FIN|Stack. It also references a CSV file and can be edited by each SI to fit their point nomenclature.\n\nChristian Tremblay https://project-haystack.org/forum/topic/548#3 auto-tagging 2017-10-05T19:03:28Z\n\nI've added this feature to nHaystack in the latest versions. Based on the name of the point, the module will look at a CSV file and add the tags corresponding to a point name.\n\nThis format allow easy sharing of tags based on names.\n\nThe module also allow to modify the file to be used so one can switch between files if necessary.\n\nReally useful when using always same names in our programs. Or for manufacturing using always the same names in their products.\n\nhttps://bitbucket.org/richiemac_77/nhaystack/src/b070b8e2ee7c8ea122878456d467c82e83697872/README.md?at=ax&fileviewer=file-view-default\n\nJohn Petze https://project-haystack.org/forum/topic/549#0 Embedded Computing Article Series on Semantic Interoperability Includes Discussion of Haystack 2017-10-05T17:54:53Z\n\nI was recently asked to contribute to a multi-part article series on cross-industry IoT interoperability from multiple industry experts being published in Embedded Computing magazine.\n\nIt's a very detailed series of articles and compares a range of semantic efforts across different industries that are part of the IoT. I wanted to make the community aware of the effort and the Haystack participation in the articles.\n\nParts 1-5 are posted on a landing page at http://www.embedded-computing.com/semantic-interop\n\nParts 4 and 5 have been the top \"semantic interoperability\" News for Bing and Google for the past few weeks:\n\nhttps://www.bing.com/news/search?q=semantic+interoperability\n\nhttps://www.google.com/search?q=semantic+interoperability&tbm=nws\n\nPart 1 is currently on the first \"semantic interop\" search page on Bing:\n\nhttps://www.bing.com/search?q=semantic%20interoperability\n\nMore articles in the series will be coming out soon.\n\nAaron Sanchez https://project-haystack.org/forum/topic/548#2 auto-tagging 2017-10-05T16:28:51Z\n\nTerry,\n\nRegarding the auto-tagging tool you've seen in two different vendors, is the auto-tagging done via the names of the points or how does the tool know which tags to apply to each point?\n\nJohn Petze https://project-haystack.org/forum/topic/548#1 auto-tagging 2017-10-05T13:04:16Z\n\nA few thoughts that may be helpful:\n\n 1. Wanted to make you aware of the Project-Builder Plus tool which has been donated to the community as open source. It includes many tools to streamline and automate tagging and accepts a range of data types as input. You can find details here: https://project-haystack.org/forum/topic/467\n 2. If you are working with Niagara systems the nHaystack tool does part of the work automatically by interpreting a range of factors from Niagara points.\n 3. We see a number of our SkyFoundry partners building tools for auto tagging to meet there project needs. Some might be of general use and some may be interested in sharing. Asking the community for comments here is a good step.\nTerry Herr https://project-haystack.org/forum/topic/548#0 auto-tagging 2017-10-05T11:19:13Z\n\nIs there any community effort to build and auto-tagging tool? Meaning, a software tool that applies tags with little or no human involvement.\n\nI know of at least two commercial analytics vendors who are or have built such a tool, but its dedicated to their product. I know of several University or DOE funded research efforts around this problem/task as well.\n\nSuch a tool would reduce the cost of deploying analytics as tagging is one of the most time consuming tasks in the deployment process.\n\nLet me know if anyone else is interested in coordinating an effort to create such a tool.\n\nJohn Petze https://project-haystack.org/forum/topic/547#0 Haystack Connections Magazine Fall 2017 Is Now Available ! 2017-10-04T15:13:12Z\n\nProject-Haystack.org is excited to announce the publication of the Fall 2017 issue of Haystack Connections magazine. Haystack Connections reports the news from the Haystack community around the world and provides updates on the development of working groups, new tagging models, reference implementations, complimentary applications, and success stories from the community as we work together to make device data easier to use across applications of all types.\n\nWith 50 pages of content from members around the world this issue provides clear evidence of the success and continued adoption of Haystack, and the growth of the community. It also includes a focus on the May 2017 Haystack Connect conference that we think readers will see great value in – even if you attended the event – as there was just too much to take in at once. And for the first time, Haystack Connections includes ads from technology suppliers that provide complimentary products, services and applications to the Haystack Community. We greatly appreciate their support of the publication.\n\nYou can find the Fall 2017 issue of Haystack Connections at this link\n\nFinally, special thanks to everyone that contributed to the content for this issue of Haystack Connections and especially to Therese Sullivan, Editor.\n\nBill Smith https://project-haystack.org/forum/topic/546#0 Niagara/Haystack Auth Patch for N4.2 2017-10-03T14:52:14Z\n\nThe authentication mechanism described in http://project-haystack.org/doc/Auth is now available for Niagara 4.2 by installing the following patch modules:\n\nbaja 4.2.36.42.3 jetty-rt 4.2.36.42.3 web-rt 4.2.36.42.3 docDeveloper 4.2.36.42.3\n\nThis will allow you to authenticate to Niagara 4.2 using the scram-sha mechanism defined in the Auth document. You should be able to obtain these through your support channel.\n\nGreg Ingram https://project-haystack.org/forum/topic/545#2 Examples of TagKinds in JSON, Zinc and CSV format 2017-10-01T14:06:22Z\n\nBrian,\n\nYup, those pages are very helpful. I believe I didn't do a good job on my post/question. I mentioned TagKinds, but I'm really looking for examples of the format others have captured for Operations and what the TagKinds look like in those examples.\n\nBeing able to see examples of real data would be helpful...\n\n 1. Where it might be a little confusing in the docs seeing 1 example for each TagKinds/Operations and\n 2. Use those different examples to test in parser/generators to have better confidence their implementation is protocol compliant.\n\nBTW... I think the docs could be improved with some of the Operations like Watch Sub/Unsub/Poll, PointWrite, etc. Once I have a better understanding, I wouldn't mind helping with examples. Just need to understand a little more :)\n\nBrian Frank https://project-haystack.org/forum/topic/545#1 Examples of TagKinds in JSON, Zinc and CSV format 2017-10-01T13:35:19Z\n\nThere is an example of each literal type in the docs for both Zinc and JSON. Plus more detailed examples for how nesting of data structures work. The only tricky one is DateTime which actually has a separate sub-section in Zinc with all the various flavors\n\nGreg Ingram https://project-haystack.org/forum/topic/545#0 Examples of TagKinds in JSON, Zinc and CSV format 2017-09-30T11:30:14Z\n\nAnyone have any detailed examples of the different TagKinds (Number, Extended String, Grid, etc.) in the different formats?\n\nThe project documentation lacks in this area and would be nice to see different examples.\n\nThanks in advance.\n\nBuddy Patton https://project-haystack.org/forum/topic/543#5 Vibration as a common VFD point 2017-09-29T18:14:11Z\n\nIt's typically measured with a sensor hooked directly to the piece of equipment that needs to be monitored but the units can vary widely based on the importance of the vibration being measured. I believe the most common method of measurement is to measure the frequency (in Hz) but I've also seen where the actual distance is measured as in mm/s.\n\nedit: I agree that this probably shouldn't be limited to VFDs\n\nJay Herron https://project-haystack.org/forum/topic/543#4 Vibration as a common VFD point 2017-09-29T15:22:01Z\n\nI think this would be a good addition.\n\nScott Boehm https://project-haystack.org/forum/topic/543#3 Vibration as a common VFD point 2017-09-29T14:42:37Z\n\nI'm no expert however what I've seen is an analog value expressed as inches/second as well as a simple binary value (true/false). Not familiar with industrial applications as Buddy suggests.\n\nBrian Frank https://project-haystack.org/forum/topic/544#1 What's the better practice, String markers for extra fidelity or new tags? 2017-09-29T12:28:05Z\n\nAs an overall rule, \"types\" are defined with marker tags (or combinations of tags). Never use a tag called \"type\"\n\nThese would parallel the \"what\" or \"subject\" of the point which is done with marker tags: air, water, steam, elec, refrig\n\nHydraulic fluid would definitely fit into that model.\n\nPneumatic is interesting because its is often air but air used in a specific way, so that would probably warrant some discussion\n\nBrian Frank https://project-haystack.org/forum/topic/543#2 Vibration as a common VFD point 2017-09-29T12:24:58Z\n\nHow is it typically measured and with what unit(s)?\n\nScott Boehm https://project-haystack.org/forum/topic/543#1 Vibration as a common VFD point 2017-09-28T17:58:21Z\n\nIndeed vibration should be a tag, however it should not be limited to a VFD as other equipment has vibration sensors such as cooling towers, chillers, fans and other machines that are prone to self-destruction.\n\nBuddy Patton https://project-haystack.org/forum/topic/544#0 What's the better practice, String markers for extra fidelity or new tags? 2017-09-28T17:08:19Z\n\nI have some pressure sensors, some hydraulic, some pneumatic. Would it make more sense to tag these as hydraulic and pneumatic respectively or would it be cleaner to do type:\"hydraulic\" and type:\"pneumatic\"?\n\nJust asking in terms of best practices. I can see from discussions on the forums that tags should be more generalized.\n\nBuddy Patton https://project-haystack.org/forum/topic/543#0 Vibration as a common VFD point 2017-09-28T16:21:22Z\n\nCould we see vibration added as a new haystack standard tag for VFDs? It's common among all of my VFD equips that the spindle motor vibration has a sensor attached in an industrial setting.\n\nAndrew Stokes https://project-haystack.org/forum/topic/538#4 Polling data from Netatmo devices 2017-09-27T20:37:17Z\n\nChris, I did download and install Pyhaystack and installed it on a Raspberry Pi, but I never got it to work, mostly through my own inexperience with Linux OSes. Although, maybe it was Pypipes... or both.\n\nBrian, right now I have a script in Python which can poll for the data and using pprint, this is the format that all the data arrives as:\n\n{'body': {'devices': [{'_id': '*********',\n\n'cipher_id': '****************',\n'co2_calibrating': False,\n'dashboard_data': {'AbsolutePressure': 1003.2,\n 'CO2': 980,\n 'Humidity': 62,\n 'Noise': 48,\n 'Pressure': 1012.1,\n 'Temperature': 22.7,\n 'date_max_temp': 1497383969,\n 'date_min_temp': 1497359852,\n 'max_temp': 22.7,\n 'min_temp': 21.2,\n 'time_utc': 1497384269},\n'data_type': ['Temperature',\n 'CO2',\n 'Humidity',\n 'Noise',\n 'Pressure'],\n'date_setup': 1366459135,\n'firmware': 124,\n'last_setup': 1366459135,\n'last_status_store': 1497384282,\n'last_upgrade': 1440322796,\n'module_name': 'Indoor',\n'modules': [{'_id': '**********',\n 'battery_percent': 100,\n 'battery_vp': 6335,\n 'dashboard_data': {'Humidity': 67,\n 'Temperature': 22.3,\n 'date_max_temp': 1446918449,\n 'date_min_temp': 1446918449,\n 'max_temp': 22.3,\n 'min_temp': 22.3,\n 'time_utc': 1446918449},\n 'data_type': ['Temperature', 'Humidity'],\n 'firmware': 34,\n 'last_message': 1446918525,\n 'last_seen': 1446918500,\n 'last_setup': 1366638628,\n 'module_name': 'Outdoor',\n 'rf_status': 32,\n 'type': 'NAModule1'}],\n'place': {'altitude': 75.891496494971,\n 'city': '*******',\n 'country': 'US',\n 'location': [******, *******],\n 'timezone': 'America/New_York'},\n'station_name': 'JP_Atmo',\n'type': 'NAMain',\n'wifi_status': 45}],\n'user': {'administrative': {'country': 'US',\n 'feel_like_algo': 1,\n 'lang': 'en-US',\n 'pressureunit': 1,\n 'reg_locale': 'en-US',\n 'unit': 1,\n 'windunit': 1},\n 'mail': '***********'}},\n\nstatus: ok, time_exec: 0.019564867019653, time_server: 1506541397}\n\nI also, through formating, can print out individual values. Is that the same JSON format Haystack follows? Really, the only value I actually care about is temperature. Which the code\n\nprint('\"Temperature\":', data['body']['devices'][0]['dashboard_data']['Temperature'])\n\nwill print out:\n\n\"Temperature\": 22.7\n\nso even if I reduce the code to just be the number value, I'm not sure how I get that value through my JACE, whether I save it and somehow get it sent to the JACE, or have something poll for the data using a similar script and send it to the JACE.\n\nJonathan Hughes https://project-haystack.org/forum/topic/542#1 haystackCall read fails for Objects with N4 Relations (Custom) 2017-09-26T20:48:03Z\n\nCustom dictionary relationship failures in the Kodaro Haystack Driver has been resolved in release 1.0.16.\n\nThis issue stemmed from the assumption that the Haystack dictionary was installed and used to create the relationships. This was a bad assumption as it should not necessarily be a requirement to use the haystack dictionary to create your tagging database in N4. The 1.0.16 correctly handles all relationships and ID resolving techniques that were previously assumed to be from the Haystack dictionary for any dictionary the relationship was created with.\n\nBrandyn Carlson https://project-haystack.org/forum/topic/542#0 haystackCall read fails for Objects with N4 Relations (Custom) 2017-09-26T19:20:15Z\n\nI'm having an issue not being able to discover objects with custom relation references in Niagara 4 using the haystackCall function. The Kodaro Haystack Driver is being used for this project so that N4 marker tags can be synced between Skyspark and the N4 database, which contains extensive tagging and N4 object relations. In order to be usable within the customer's custom tag dictionary, the relation references for siteRef, ahuRef, and equipRef (in addition to some others) have been configured within their custom tag library and applied to site, equip and point objects across the N4 database. Therefore, haystack tag dictionary is not being used.\n\nWhile the haystackCall function can discover objects using neql filters for tags within the customer's custom tag dictionary, it appears that the only point or equip objects are discovered/returned using the haystackCall function are those without any relation references. The same query that returns 500+ objects with an \"equip\" tag in N4 returns 0 records upon a haystackCall read with the same exact filter.\n\nIs there an inherent issue for the haystack protocol or haystackCall function to interact with N4 objects with (certain types of) relation references? I'm working with Kodaro to troubleshoot the issue from their side but I wanted to reach out to the forum to see if this is a known issue or limitation associated with the haystack protocol?\n\nThanks!\n\nStephen Frank https://project-haystack.org/forum/topic/539#1 Two-speed Fans 2017-09-25T14:37:32Z\n\nI think the fan cases covered right now are simple on/off or on a VFD. I don't know that I have the right answer for you, but you could consider using speed with discrete percentage values, or could consider using run + stage (1,2) along the lines of cooling/heating equipment.\n\nChristian Tremblay https://project-haystack.org/forum/topic/538#3 Polling data from Netatmo devices 2017-09-25T14:36:54Z\n\nI would try to make a driver in the Jace that would poll the info directly... Or maybe only a small script that reads from a URL if sufficient.\n\nOr you will need a 3rd device between the 2 everytime...\n\nBrian Frank https://project-haystack.org/forum/topic/540#3 Marker Tag format in JSON when not used 2017-09-25T00:12:15Z\n\nYou don't need name - I just copied that from our software and we add a few more columns\n\nGreg Ingram https://project-haystack.org/forum/topic/540#2 Marker Tag format in JSON when not used 2017-09-24T23:23:01Z\n\nThanks Brian, I will review and update my code.\n\nI have another question based on your example. It appears you added a column for \"name\". This is not shown as a property/column in the Formats section in documentation. Which one is correct? To include \"name\" or not include?\n\nThanks again for the help.\n\nGreg Ingram https://project-haystack.org/forum/topic/541#2 Getting 404 Not Found errors on Download page 2017-09-24T23:17:39Z\n\nNo problem. Thanks for the fix.\n\nMatthew Giannini https://project-haystack.org/forum/topic/541#1 Getting 404 Not Found errors on Download page 2017-09-24T22:59:20Z\n\nGreg - this has been resolved. Sorry for the inconvenience."