Jump to content

cjcilino

NI
  • Content Count

    10
  • Joined

  • Last visited

  • Days Won

    1

cjcilino last won the day on July 31 2018

cjcilino had the most liked content!

Community Reputation

5

About cjcilino

  • Rank
    Active

Profile Information

  • Gender
    Male
  • Location
    Austin Texas
  • Interests
    LabVIEW Architecting!
    Tinkering with all technology!
    Digital Photography
    Violin
    History

LabVIEW Information

  • Version
    LabVIEW 2017
  • Since
    2004

Recent Profile Visitors

1,163 profile views
  1. My apologies for not having much info on this page yet. I'm just trying to get the code in a presentable state and then I'll broadcast it's purpose and stuff.... And Cirrus Logic is not affiliated with NI. I'm not sure why my profile reads "NI"... hmmm.... I'll see if i can get that squared away.
  2. Overview At Cirrus Logic, I'm responsible for creating applications and frameworks to improve the efficiency of our validation department and ultimately lower the cost of validation. I'm also Description UML and APIs All UML and API documentation are included in the Word document per released zip file Software Requirements LabVIEW 2017 Release Notes 1.0.0-11(Watchdog 1.0.0-11.zip) Fixed spelling errors and regenerated documentation. 1.0.0-9 (Watchdog 1.0.0-9.zip) Refactored locations of files on disk to be more structured Completed documentation Using timestamp for timeout perpetrator. Updated example with instructions 1.0.0-3 (Watchdog 1.0.0-3.zip) This is the initial release. Very very alpha
  3. Have you ever needed to programmatically generate a report documenting your LabVIEW Classes? I've released an alpha version of my auto-documentation utility I designed and implemented at Cirrus Logic (http://bit.ly/ChrisCilino_AutoDoc). I designed and created the software in 4 parts. 1) An Atlassian Confluence API, 2) An Atlassian JIRA API, 3) A Class Report generation API, and 4) Two very small "applications" the demonstrate the API's usage. Not only can the APIs \ examples document your code, you can also generate JIRA tickets for the parts of your documentation you're missing. I hope you'll find this software as useful as we at Cirrus Logic have. I would consider it "mid alpha" quality, but intend on investing in it over time. You can find the software at http://bit.ly/ChrisCilino_AutoDoc Here's an example of a generated report for the members of a class The private data also has its own table that looks like There are many more features to the report, not to mention the APIs used to generate the reports. Also I've created an application to generate JIRA tickets that list the missing parts of a report. Enjoy!
  4. Overview At Cirrus Logic, I'm responsible for creating applications and frameworks to improve the efficiency of our validation department and ultimately lower the cost of validation. In order to quickly and efficiently turn source into applications and frameworks for distribution, a build system was necessary to abstract away the conversion of source into the different types of deliverables (VIPackages, Executables, dlls, ect) consumed by my end users, as well as abstract away the build order of our hierarchical re Many have undertaken to solve this problem. I don't claim to have created a silver bullet. But I do hope that the system I've put together (and am releasing as open source) will act as a starting point for you to extend and customize to meet your needs. I've endeavored to employ good software development principles including separation of concerns, and the SMoRES principles. I'll be the first to volunteer that it isn't perfect and as always, our best software is constantly a work in progress. However, I believe the build system is at a stage to be at least moderately helpful to a handful of people in our community. Description At NIWeek 2018 I gave a presentation on the build system. You can find the pdf of the presentation here: https://event.crowdcompass.com/niweek2018/activity/rQM8g1QHz2 and I've attached the PDF of the presentation below. The Application's UI The UI is designed to guide someone through the build process, allowing them to select what components or exports they would like to build, if and how they would like to be notified about the build, auto submission options, and source code control. I've attached a small video titled "Build UI Demo.mp4" below. UML and APIs All UML and API documentation are included in the Word document per released zip file Software Requirements LabVIEW 2017 NI Application Builder VI Package Manager Pro Other dependencies are listed in the Instructions per zip file. UML Overview As of 1.4.0-58 the UML looks like: Build UI Demo.mp4 Release Notes 1.4.0-85 (Component Builder 1.4.0-85.zip) This is a major refactor in the SCC API. I've modeled the p4 label with a new api. This release is primarily as an intermediary release. I intend on breaking SCC out of the component builder into its own separate component in the next release. 1.4.0-81 (Component Builder 1.4.0-81.zip) Created a "proxy" api for VI Package manager interactions. Sometimes the VI Package manager api would hang. So I now call by reference and will kill and restart VIPM if it doesn't respond in time. 1.4.0-75 (Component Builder 1.4.0-75.zip ) Fixed reference counting for executable builds. 1.4.0-73 (Component Builder 1.4.0-73.zip) In the case where a user has specifically unchecked "auto increment", the build process will auto increment the build. Builds must be auto incremented. I've released a new build of the container that has a minor bug fix. Added file utility tools to aid with using "net use" to move and copy files across the network. 1.4.0-59 (Component Builder 1.4.0-59.zip) Minor spelling error in component template: "componet". Added documentation for the Custom Install Step Launcher. Added build instructions for Custom Install Step Launcher. 1.4.0-58 (Component_Builder_1.4.0-58.zip) Added the ability to export NI-Source Distributions, NI-Executables, NI-Insatllers, and NSIS Installers Released a template component that exports an NI Package and VI Package including step by step instructions Released "Custom Install Step Launcher" to execute VIs as pre install, post install and post install all actions for NI Packages. Released comprehensive documentation included in the zip file. Component_Builder_5_31_2018.zip Component_Builder_10_11_2018.zip
  5. With NIWeek 2015 around the corner community events like the "World's Fastest Coding Challenge" are getting spun up. Another one of my favorite community event is the "Challenge the Champions", a competition between 5 LabVIEW Champions (including the new LabVIEW Champions being inducted at NIWeek 2015) and 5 challengers who think they can usurp these leaders of the LabVIEW community. In case you're unfamiliar with the LabVIEW Champions program you can find out all about it at bit.ly/lv_champions. I already have three challengers who'll definitely give the Champions a run for their money lined up. So I'm looking for two brave souls to step up to the plate on Tuesday evening, August 4 at 6pm sharp. To those two challengers out there, please send me a private message by Wednesday July 29th. Fame and glory await! NIWeek 2015... 8 days and counting! All systems go!
  6. NIWeek 2015 is just a few short weeks away! Community is a huge aspect of NIWeek and one of the most popular and fun community events is the “World's Fastest LabVIEW Programmer†competition. This prestigious title has been successfully defended by NI’s own Darren Nattinger (and if you’ve ever seen him compete you understand why). But this year Darren has announced his retirement from the competition and will go down in history as undefeated for 7 straight years beginning in 2008. While we’re sad that he won’t be competing, that means there will be a new name inscribed on the coveted trophy! For those of you unfamiliar with the event, the “World’s Fastest LabVIEW Programmer†is a competition to see who can best take advantage of the many LabVIEW IDE tools, like Quick Drop and a vast array of APIs, that make it easy to crank out code at breakneck speeds! Visit bit.ly/lv_fastestcoder to learn more. Your journey to the trophy begins at the “LabVIEW Coding Challenge†kiosk in the LabVIEW Zone on the NIWeek expo floor. There you’ll face three challenges designed to put your lightning fast LabVIEW skills to the test. The two fastest competitors will be brought up on the Technology Theater stage Wednesday evening of NIWeek at 5 pm in a live, face to face race to the finish. And of course, spectators are welcome to cheer them on! Think you have what it takes to be the next World’s Fastest LabVIEW Programmer? Step up to the kiosk and let the race begin .... glory awaits!!
  7. Totally looking forward to the BBQ!!!
  8. Howdy! It's getting close.... NIWeek 2014 is almost upon us! To celebrate I put together a video for the LabvIEW Coding Challenge (linked below). To qualify for a chance to go up against Darren, visit the LabVIEW Coding Challenge in the LabVIEW Zone of the expo floor and test your skills. The two fastest coders will go head to head for a chance to go up against Darren, the world's fastest LabVIEW coder! The competition is at high noon on Thursday, August 7. I've personally written the questions and this year will be entertaining and fun.... I guarantee it. Darren's Coding Challenge Chris Cilino Certified LabVIEW Architect
  9. Hey MarcCG, Thanks for the props! It's kinda funny. I've created some "hidden VIs" for my own purposes and one of them is to return an array of references to each node in the tree. In effect I flatten the hierarchy into an array so that you can touch every element. After install, the vi is located at ..vi.lib_ApplicationToolsContainersContainersContainerTestsTesting UtilitiesReturnEntireHierachyofContainers.vi Hey drjdpowell The Containers are by-reference. I didn't want to create copies of Containers in the tree so I store references to children in parents.
  10. Well.... here it goes. This is my first LAVA post and I'm pumped! Figured I'd start out by asking for ya'lls (yes I'm from Texas) opinion on a side project I've had in the works for a while. I've developed in LabVIEW for just about a decade, even before my career at NI, and I've run into cases where I wished the array shared some of the characteristics of the cluster and the cluster had some attributes of the array. For example, I wish I was able to name and index my array elements by name like you can with the cluster while also not having to hard code that name on the block diagram with something like an unbundle. Almost like a dynamic unbundle by name... or something like that. So I've put together something I call the LabVIEW container that has the "dynamic-ness" of an array and the hierarchy mixed type named data "feel" of the cluster. It also behaves like a tree because of the "One parent - Many child" model. Here's a super short 5 minute video describing the concept and demonstrating a functional prototype. I've also created a community document that goes into much more detail and from which you can, if you so desire ( ), download the Container and give it a spin. I'm still doing a TON of cleaning under the hood, and adding things like VI documentation at the moment, but I'd like to get ya'lls feedback on the usefulness of the idea and thoughts on the API. This is something I'm really excited about and I hope that it benefits the LabVIEW community. Thanks ya'll!!!! Chris
×
×
  • Create New...

Important Information

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