crelf

Wow - there's already over 100 tickets sold! Get yours now before they run out

It's that time of year again. What will the next installment of the LAVA BBQ bring? One thing is for sure - door prizes galore!

Past prizes have included (just to name a few): home-made creations, gift-cards, tablets, books, IPods, LabVIEW goodness, software, bottles of Truchard wine, Ardunios, Zunes, copies of VIPM, Symbio GOOP Development Suite licenses, signed books and even a few plane rides (yes, you read that right).

Be creative! By donating a prize you and your company will receive free advertising in this thread and bragging rights on the night, so what are you waiting for? Check out the cool prizes below (knowing there will be more added to this thread as NIWeek approaches), and try to top them. If you would like to donate (please do, we really appreciate the LAVA-love) feel free to add a prize below with the details.
 

If you haven't already, get your 2013 LAVA BBQ tickets here!

I used that language professionally years ago... please don't dredge up those nightmares.

I kinda miss FORTRAN77.

"...every time you make a singleton, God kills a start-up, two if you think you’ve made it thread-safe."

Abstractions are like peanut butter; a layer or two is fine, but once you’re down five or six layers and nothing has fucking happened yet you’re in definite “even if I could get my mouth open to scream now, that would just let in the evil stuff

Brilliant!

I'll be there!  First timer.  No hazing I hope

 Mwuuuhahahaha!

Looking forward to the BBQ.  A word of advice from a previous mistake: wear shorts!

Agreed - the year Norm turned up without any pants on still haunts me.

PS: got my ticket

...how do I know that this funky bit.ly URL, with its garbled characters, is actually going to the reputable URL that it claims to be going to?

You can't. Same way that you can't be sure that any url is actually going to the reputable URL that it claims to be going to. The main difference is that bit.ly doesn't even pretend to be taking you to a reputable URL. Why? Because bit.ly isn't about trying to represent anything that's trustworthy - it's about whether you trust the bit.ly's link *poster*.

tl;dr:

Take the bit.ly URL and add a + to the end of it. This brings up the statistics page for that bit.ly link AND it displays the real URL that the link goes to. Then you can copy/paste that real link into your browser or, if you don't mind the tracking, you can go remove the + and let bit.ly do the redirect for you.

Okay, that is kinda neat - thanks for sharing.

Note: the @lavag twitter account uses bit.ly exclusively as our link shortener. Why? Because we like to occasionally look at which of our posts interest our followers: bit.ly gives us stats on that, so we can better hone the types and frequency of tweets. So there.

Still waiting for my goddamn tshirt...

It depends on what your version of LabVIEW is - it's possible that VIPM uses a different RTE (which it installs itself), so if you installed LabVIEW, installed VIPM, then uninstalled LabVIEW it's possible that LabVIEW either blew away a VIPM dependancy (eg: RTE). So you could reinstall LabVIEW and then reinstall VIPM again - then all should be well.

Or reimage

Love it!

Enable Disable Private Methods.png

.

All unsaved will be what?!?! Don't leave me hangin'!

A meme that's sweeping the interubes: http://knowyourmeme.com/memes/harlem-shake

Here's some of my favorites so far:

• and, of course, of very own Deidre's Jive:
  
  

What are your favorites?

You got me excited for a second because that sentence made me think perhaps one could attend without being a CLA. Alas, 'tis not so.

If you're not a CLA, you can buy a ticket to the summit here: http://sine.ni.com/nips/cds/view/p/lang/en/nid/13477

Val,

 

One of the advantages of being my own boss is that I already convinced her to let me go not only to one, but both!

 

Fab

Can I work for you please? The Euro summit is in Paris this year

• Addmission to the summit is free for CLAs.
  

rather than buy a premium account just to get more space

There's more than more space that comes with a Premium Account - there's the pride that comes from knowing you have financially supported the community

V I Engineering, Inc has immediate needs for Systems Engineers and Senior Systems Engineers (reporting to the Engineering Manager)

• Company: V I Engineering, Inc.
• Locations: Positions available in our Farmington Hills, MI Office
• Salary/Wage: $negotiable
• Status: Full Time, Employee
• Relevant Work Experience: 5+ years system integration (LabVIEW/TestStand experience preferred, but not required)
• Career Level: Intermediate (Non-Manager)
• Education Level: Bachelor's Degree
• Residency/Citizenship: USA Citizenship or Greencard required
  

Driving Business Results through Test Engineering

V I Engineering, Inc. has a vision for every client we engage. That vision is to achieve on-time and on-budget program launch more efficiently that the competition. To realize this vision, customers need to achieve predictable test systems development, eliminate waste in test information management, and drive increased leverage of test assets. An underlying requirement for all of these areas is metrics tracking and measurement based decision making.

Job Description
Ready to make a difference? Bring your experiences and skills to the industry leading test organization. Help us to continue to shape the way the world views test. We are seeking a talented Systems Engineers and Senior Systems Engineers to be responsible for technical execution of successful projects in the Medical, Military, Transportation, Consumer Electronics and Aerospace Industries. The position will have high visibility to customers and vendors. This is a very fast paced team with close customer contact and strong career development opportunities. A large part of the position is to identify, own and drive technical design and development of test systems. You will work alongside other like-minded and equally talented engineers, and be creative in a fast-paced and flexible environment that encourages you to think outside the box.

Required

• 5+ years of Systems Integration experience
• Experience in Design and Implementation of Test Systems, including integration
• Experience in ATE usage and development
• Experience in reviewing of Mechanical Fixtures
• Experience in understanding the design of Circuit Boards as they relate to a total system
• Experience in Taking Part in Technical Teams throughout All Phases of Project Lifecycle
• Experience in Interfacing with Sub-vendors and Customers
• Ability to Multitask
• Comfortable Working on Various Team Sizes
• Excellent Communication Skills
  

• Requirements generation and review experience
• National Instruments Hardware knowledge
• LabVIEW/TestStand experience
• Experience with Source Code Control (SCC)
• Experience executing verification and validation for projects
• Experience generating and/or reviewing cost proposals
• RF Technology (DAQ, General RF Theory)
• FPGA (with LabVIEW)
• Professional software engineering processes and metrics experience (statement coverage, code size, reuse measurement, etc)
• TortoiseSVN
• V I Package Manager (VIPM)
• UML
• Experience with Projects for Regulated Industries
• MS Project
  

Formal Education

• Technical degree (BS Engineering, Computer Science, Physics, Math)
• National Instruments Courses a plus
• National Instruments certification a plus
  

Notes:

Expected Travel Time is up to 25%.
Relocation assistance is possible.

V I Engineering, Inc. offers incredible opportunities to grow and advance your career, a dynamic work environment and the flexibility of a small company.

The Test Software and Integration Group values innovation, out-of-the-box thinking, high-tech toys and a fun / amazingly collaborative working environment. We're a National Instruments Select Integrator, and we're the closest you can get to playing with all the pre-released and new NI toys without joining the NI R&D team - and we get to play with them in the real world.

To apply for this position, email a cover letter and resume to jobs@viengineering.com with the subject "Systems Engineer employment application (referred from LAVA)" or "Senior Systems Engineer employment application (referred from LAVA)".

You can go for me, next time!

Pretty sure the US Government might take issue with that

Is there a link to the wiki from LAVA? Perhaps there should be a prominent one. I always forget the LabVIEW wiki exists, and had to Google it to find it.

LAVA 1.0 had a link in the bar below the banner - not sure what happened to it. If you want it back, report this tread to get the admin's attention.

Off Topic again; the reason for sub-routines got a much better explanation now....

Well played.

For reference (and open to ppl improving): http://labviewwiki.org/State_Machine

There was some talk at the BBQ of some revamp work of the LabVIEW Wiki and want to volunteer my services. What I wanted to understand is what do we prioritise, are we just trying to repeat the LabVIEW help, or keep tips and tricks or some combination of the two? Either way I might try and start on some of the stubs.

Excellent timing! There was a meeting of the minds of a few prominant LAVA-ites on Wednesday to start making this a priority. The new LabVIEWwiki fearless leaders are our very own David Corney and Mark Yedanik (assisted by Mike, me and Chris Roebuck). I suggest anyone interested PM Dave and Mark to get on the team.

Then I just have to squint a lot at my laptop screen when I'm scrunched up in a dark corner on some submarine trying to do code changes.

I know it's off-topic, but that sounds so cool!

I have a pile of Kudos on a different forum because that is a patently false statement.

1. Substitute html or pdf for chm and I like this option.

The tool we have in house builds html, builds the chm from the thml, then deletes the html - one of the most used features is a checkbox that keeps the html that's generated

Why? Because the html is easily indexed by our internal sharepoint system - which kind-of ties into the intranet wiki idea.

• Building .chm files and then linking them to controls and menus in my application. (not sure exactly how to do this).
  
• Using tip strips to supply documentation.
  
• Using a pane on the window to display help messages when requested or when hovering over certain controls.
  
• Linking to a Wiki on the corporate network.
  

I don't know your corporate culture, but I'd say go for the first three at least. We have a documentation generator (it's old and clunky now) that does it (it sucks up all the VI descriptions, control documentation, etc, and puts them into a chm, and then adds the relative links to each chm page back into the context help for each referenced VI), and it works well for the end-user.

PS: "Using a pand on the window to display..." - I suggest you just use context help for that - it's free, it's easy to use/maintain, and is a simple keyboard shortcut away. Honestly, I think it's one of the most under-used features in custom LabVIEW apps: everyone uses it within the development environment, but hardly anyone uses it in their apps.