PySTDF 1.3.1 Released, New Downloads Page
I recently learned of a bug in the AtdfWriter implementation. The issue was a method intended to format array types that never got written (oops!). I've added the method, so the stdf2atdf should run more smoothly now.
I was also pleased to discover new features available on Google Code: Wiki support and a Downloads manager. The latest release, 1.3.1, contains the above ATDF array formatting fix, and is now available on the PySTDF downloads page.
I was also pleased to discover new features available on Google Code: Wiki support and a Downloads manager. The latest release, 1.3.1, contains the above ATDF array formatting fix, and is now available on the PySTDF downloads page.
posted by casey at 8:38 PM
4 Comments:
Hi! I think you have an interesting tool there. I can't agree with you more on the STDF warts! "Broken, dirty data" - right on! I'd like to know if I can use this at my work place, to troubleshoot the STDF issues? (sidetrack: I'd doubt that anyone will just play with STDF for fun :-D)
Hi Chuan!
Who says semicon data analysis can't be fun? Solving problems with data is lots of fun! Of course, you'd probably be doing this at work -- I don't know many ppl with recreational ATE equipment in their garage! :)
Please feel free to use PySTDF at your workplace, this is why I have released it open-source. You should be aware that PySTDF is released under the GPL (GNU General Public License), and there are some implications applications that use GPL software. I will follow up soon with a primer on the GPL license.
In a nutshell, if you are not going to distribute a closed-source application that uses PySTDF, there should be no conflict with the GPL license. For example, your own private data analysis should be fine.
The GPL license only places a restriction on the distribution of code, in source or binary form, that is built on top of GPL software.
I would be open to selling a commercial license for PySTDF that allows proprietary, closed-source distribution. Pricing would be flexible and startup-friendly, based on the particular application, size of customer, support level, etc.
Wow, thanks! this is great! Loved the app! I'm not doing developmental work on STDF format, just troubleshooting STDF problems from sub-cons. No doubt, semicon data analysis is fun, but it is not if you are having malformed STDF from other ppl and can't tell them what is missing in their STDF! For example, STDFExplorer is great to show them "hey look, your SBLOT_ID is blank!" etc etc. Hehe... :D Cheers!
Hi Casey
First, I like the tool and think it great.
As I am new to ATE industry. I have the following
question on the tool.
1.The tool show wafer, insertion and part on the left
hand side of the grid. What does these columns mean ?
I am looking at designing a database structure to store
these data structure. Any help or advise is much appreciated.
Suggestion to tool
1.Have search feature for looking at specific record type
and better still, have search feature with multiple criteria
like looking for a record type and wafter = 1.
Currently, I have to scroll the grid to find a specific Record
type.
2.The left hand side grid should be adjustable as it have more
column to display instead of the right hand side grid (since it
only have 2 columns)
Thank.
Post a Comment
<< Home