Userfields and Table files

[[Ma...]]

Hi

I have a question, at our company we have used the userfields made by us and Table files for export data for the last 5-6 years, now we want to use the report header fields (parameters) and Q-DAS export which are default in Calypso and also the PiWeb report.
I got in contact with Zeiss application engineer and he told me that i have to change it in every program there is no way of change these settings for all programs at ones (we have 300+ programs). 😐

So if any of you has a way of doing it in a smart fast way i would be very thankfull.

[[No...]]

I think the app. engineer is right. It's like that with a lot of program specific settings in Calypso: If you want to change them in all measurement plans, you have to do it one by one.

There is a very small chance that all or part of it might be doable in a quicker way, namely by manipulatiing the inspection (and maybe inspset) files directly. But you would first have to find out what exactly has to be changed (this could affect multiple locations in each file), and then either do it one by one with Notepad - which is quicker than Calypso, but only slightly less tedious - or find a program that is able to perform search/replace functions in multiple files at once. Quite error-prone, if you ask me.

[[Ma...]]

Until someone make an utility for this and similar needs 🤣

[[Ma...]]

Please sign in to view this quote.

I think i will investigate what changes there are made in these files, i know that there is a program like notepad with find and replace options.
This would be a great task for the new Calypso update, possibility to make "Global changes" for all measuring programs.

[[No...]]

Please sign in to view this quote.

Let me give you some initial aid:

#(
#elementToStatistic ' ->' 
#on) 

This is set in the inspection file for every characteristic that shall be sent to the QDAS file (corresponds to the setting in the characteristics editor). The tricky part is to find out where and how it has to be inserted. The file format has a lot of nested data structures which look quite repetitive. Every bracket counts, so it's hard to tell where this should go if it's not already there. Good luck!

[[Ma...]]

If you are familiar with Total Commander, then you can use "compare" to highlight changes.

If it's not too much changes, you can use LUA to perform changes - it's just text file which is interpreted by LUA.exe - so changes can be done instantly on place.

[[Ma...]]

Thanks for your ideas, now i have only to do the work.

[[No...]]

Please sign in to view this quote.

I prefer old-school AWK 🤠
Honestly, I don't even know LUA, but it sounds like they do similar things.

[[Ma...]]

Please sign in to view this quote.

I didn't know about AWK 🤣 It's older than LUA, so in some way it can work or it will be more difficult to achieve.
If you have younger IT then they can allow you LUA, otherwise they will demand AWK 🤣

[[No...]]

Please sign in to view this quote.

I've been using AWK a long time ago when we still used UMESS-UX. AWK is part of the UNIX system, so it was natural to use it. We always had problems with the QDAS converter not being able to correctly process the ASCII protocol file (UMESS didn't use table files). It was because I had inserted some special characters in the protocol header, which QDAS couldn't cope with.
So I made a small AWK script to eliminate those characters from the file before feeding it to the converter.

AWK is quite handy for simple tasks like this, but as far as I remember, it didn't feature as many commands as LUA. But hey, convenience is for sissies 🤣