1 / 21

Status of Database Interface for Bonding Data

The upgraded Database Interface (version 0.2) for Bonding Data is now available as a DEMO, closely mimicking the future version's interactive design. This release addresses feedback from version 0.1, ensuring data visibility only through authorized user views. With 11,000 lines of code, it features a functional description that supports user actions such as search, view, and update. Future updates will focus on user documentation, installation procedures, and improved interaction with the TrackerDB for hybrid bonding data management.

glenna
Download Presentation

Status of Database Interface for Bonding Data

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Status of Database Interface for Bonding Data Salvatore Costa University and INFN – Catania

  2. News • Version 0.2 released on 17 Oct 2002 (eventually!) • DEMO, but with same interactive look-and-feel of future real version for the User • Takes into account all comments to previous v 0.1 (example: VIEW requires pw, so data are visible only within CENTER) [if not: complain] • 11,000 lines of code (HTML, pl, XML)

  3. Functional Description if data front page ID_oper.dat SEARCH ENTER op VIEW UPDATE ID_oper.dat ID_oper.xml results ParSet…dat ParSet...xml VALIDATE su CREATE new file BigBrowser User’s Guide (in new window) ID_oper.xml.indb ParSet….xml.indb man indb TrackerDB

  4. Work in Progress on v0.2 • Fix bugs [already fixed some] • Soften bg colors (OK on LCD monitors, too bright on CRT) • Add “defaults” to Forms for some CENTERS

  5. Center “DB Readiness”

  6. Work to do for v 1.0 • Write User’s Guide • Develop Installation procedure • dir designation and naming (results and indb must coincide with those declared when installing BigBrowser) • BigBrowser on same machine or in machine mounting same dir • Web server configuration • Authentication (pw) • Authorizations (dir ownership and protection) • Make it “Talk” to TrackerDB • Extend to Hybrid Bonding…

  7. “Talk” to TrackerDB… …to get List ofChannels not-to-be bonded • Sought solution: Download when entering Pre-Bonding • Try “Relay” application to query TrackerDB from User’s program • Backup solution: Use BigBrowser to download SENSOR Tables, then filter list with script (Andrey Starodoumov helping) Will be documented in User’s Guide

  8. “Talk” to TrackerDB… …to upload our data • No Relay application,AFAIK • Using a button in BigBrowser Will be documented in User’s Guide I need to determine exact XML file contents

  9. XML file contents <?xml version="1.0" encoding="UTF-8" ?> <DBFile xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <xsi:noNamespaceSchemaLocation="calibration.xsd"> <object id="111" /> <action> <action_description name="PREBOND" version="1" object_name="MOD" object_type=“TIB4" input_id="123" /> <result name="centre_name" value="SANTA BARBARA" /> <result name="tool_id" value="2" /> <result name="tdate" value="2002-10-17T18:16:37" /> <result name="INSPECTOR" value="Susanne Kyre" /> <result name="RECV_TIME" value="2002-10-17T18:16:00" /> <result name="UNPACK" value="None" /> <result name="STATUS" value="Good" /> <result name="QUICK_TEST" value="No comment" /> <result name="STORAGE" value="None" /> <result name="SHIP_TIME" value="2002-10-17T18:16:00" /> <result name="READY_FOR_BOND" value="yes" /> <result name="status" value="valid" /> <result name="tcomment" value="nocomment" /> </action> </DBFile> …

  10. “Talk” to TrackerDB… …to pass List ofChannels not bonded from Bonding Center to Bonding Repair Center • In DEMO Bond Repair forms look in file created by Bond Forms • In v 1.0 must dowload from TrackerDB since Repair Center may be different than Bonding Center, just as has to be done for the list of channels not-to-be-bonded

  11. Hybrid Bonding • “8th Section” in Interface?, such as Hybrid Bonding Enter Data Add or Change Data Validate Data • Added to the “Bonding” Forms? • Most depends on when Hybrid bonding occurs, after Module is assembled or before? • To which OBJECT (as registered in TrackerDB) should we attach the info: MOD or HYB or...?

  12. The 9 Bonding Tables “BOND” Composite

  13. “PREBOND” Table

  14. “BONDMACHINE” Table

  15. “BONDWIRE” Table

  16. “BONDLOG” Table

  17. “BONDSTATUS” Table

  18. “POSTBOND” Table

  19. “BONDREP” Table Bonding Repair Forms also write back into BONDSTATUS Table (and increment VERSION):

  20. “PULL” Table

  21. “BONDPARAM” Table Example: LOOP_HEIGHT: 6 um PULL_UP: 50 whatever PULL_DOWN: 99 Etc…

More Related