FAQ¶
This is a collection of occasionally and frequently asked questions which come up for the ITk Production Database. Please look here for answers. A Twiki version of the document is being maintained as well.
Who should I ask when I have a problem?¶
If you encounter bugs, error messages or similar problems, use the issue tracker within the database to submit a bug report (click on the arrow next to your name and then click on Report Issue). If you don't know how something works or how to approach a specific problem, please contact someone!
| Contact | Reason |
|---|---|
| Jiayi Chen | strips-related problems, feature requests for database |
| Monika Wielers | pixels-related problems, feature requests for database |
| Andy Blue | database-related problems |
| Bruce Gallop | software-related problems |
| your activity coordinator | suggestions for components or tests you work with |
Is this the final version of the database?¶
The initial version if the database is so so-called test version: it gives a lot of freedom to people to test things, create new components and tests and test the functionalitites, it is not the final version of the database. Projects will migrate to the production version of the database, when all the components and tests are sorted out and no major changes are expected. Transition to the production database will mean:
- a reduction of the number of component managers and institute authorities to avoid changes which could cause damages
- full storage capabilities, i.e. possibility to upload high resolution images and large test data files
- final structures (components/stages/tests/naming conventions) for everything that moves
We will keep the test version of the database to test concepts.
Why can I not register components in the database?¶
Check out the tutorials for more information.
In order to register components, you need to:
- be a registered user of the database (see database tutorials)
- be associated with an institute (see database tutorials)
- be at least an executive at your institute
- be a member of an institute that is allowed to handle this component (see database tutorials)
What are the different levels of users in the database?¶
Readers¶
Users who can view registered components, test run results or component type descriptions. These users can add notes to components or tests, upload attachments etc.
Executives¶
In addition to "Readers" level + rights. Users of who can register components and upload test run results.
Institution Authorities¶
In addition to "Readers" level + rights. Users who manage components and test run results related to the institution managed by them. Users are able to delete or confirm the deletion of records. Users also manage other users cooperating with their institution.
Component Managers¶
In addition to "Readers" level + rights. Users who manage types of components and tests, can modify component stages and properties.
Can the database handle things like wirebonders, tools and other objects which do not go into the detector?¶
Yes, there is a dedicated component category called "reusable", which can either be reused indefinitely or can have a counter (to be implemented) which counts down the remaining number of allowed uses until the item becomes unsuable.
Can the database handle batches?¶
Yes, batches can be set up for each component type or even for other batches: under the menu point "Batch types", a new type of batch can be defined (e.g. a batch of sensors, hybrids, ASICs etc) and the relevant components in that batch can be added (e.g. batches of ASICs contain both the wafer and the ASICs on the wafer). After defining that a component comes in batches, each newly registered component will have a field asking for the batch number. When entering a batch number, the database checks if this batch number exists already and will either associate a component with the existing batch or create a new one.
Tests can also be defined for batches instead of individual components: when defining tests for components, each component has to pass the test. When defining a test as Batch QA/QC, only a specified number of components from that batch or a certain percentage of components from that batch need to have the corresponding test results uploaded and passed for the whole batch to pass. When the required tests for a batch are completed, all components in that batch will be marked as "batch QC passed".
What is the difference between a test property and a test parameter?¶
Philosophically, tests properties are inherently known at the time of the test and could be filled in ahead of time: which machine is used, which bias voltage is used, which temperature was set.
Test paramaters are inherently unknown at the time of the test and need to be measured to be entered: things like noise levels, leakage currents and pull strength.
Practically, it is currently only possible to set thresholds for test parameters, not for test properties. If thresholds should be set for the database in order to evaluate test results, those need to be defined as test parameters (currently)
What is the difference between a "Created" and an "Active" test?¶
Check out the component and test creation tutorial, (slide 29 in original version).
What are "Additional parameters" of a test?¶
Check out the component and test creation tutorial, (slide 26 in original version).
What is the difference between "Fail", "Trashed", "Deleted" and "Rework"?¶
Fail: something was out of spec at a test and is therefore a failure
Trashed (different from Fail as it is outside the normal assembly process): if things fail as part of the assembly process, they fail. If something fails because someone dropped a sensor or someone applied the wrong voltage or whatever, they were accidentally broken and are set to trashed (no possibility for repair).
Deleted (for more abstract errors): components which were accidentally registered as the wrong type, serial number, institute etc. Deleting should only be used to correct for those types of problems (e.g. to correct the creation of components in the database which don't exist in reality in that shape or form), not for problems with existing components. Deleted components are not actually deleted, but removed from the searchable database area and can be retrieved if deleted accidentally.
Rework (similar to shipping): it's not an actual stage, it can be chosen at any stage and can be used to revert to an earlier stage of the component (e,g, if something breaks during testing, you can revert to wirebonding stage). We also have a feature request to permanently mark these as reworked.
Does this mean deleting a component will cause a problem when trying to re-register another component with the same serial number?¶
No. When creating and deleting a component with a specific serial number, a new component with the same serial number can be created lated without duplication conflicts (as deleted components are not checked for serial number duplications).
What happens to assemblies that are being trashed?
The general rule is that trashing or deleting a component affects all the assembled components up to that level, i.e. the component itself, its children, grandchildren and great-grand-children. Trashing a module assembled to a stave will trash that module, its hybrids, powerboard and sensor and any ASICs assembled to the hybrid and powerboard, but does not affect any other modules on the stave or the stave itself (except for the module being disassembled).
Why can I not assemble my component to this assembly?¶
There are a couple of common problems that should be checked:
- you or your institute need to be the owner or current location of the assembly and the component to be assembled
- the component you want to assemble needs to be the correct type, sub-type, and can not be trashed, deleted or broken - potentially it needs to be in its final stage.
- The component supposed to be assembled can not currently be assembled to another component (i.e. have another current parent)
- the corresponding position on the assembly needs to be empty
What is the difference between serial numbers and component codes? Can I re-use the serial number of a deleted component? Why is my search for a new component finding a deleted component instead?¶
The database has two different ways to identify a component: serial numbers and component codes. When a component is registered, the database assigns a component code which is unique. Even if the component is deleted, the component code is not re-used but remains associated with the now deleted component.
The serial number of a component should be unique, but due to errors in registration, it is possible that two components are accidentally registered with the same serial number. In that case they can not be distinguished by serial number, but can still be distinguished by compnent code.
If a component with a unique serial number is deleted, it is not listed anymore and the deleted serial number can be re-used for a newly registered component. However, the deleted object still exists, associated with the component code, in the database and can show up in searches.
What happens if I want to ship an assembly or part of an assembly?¶
An assembly consists of a parent (the assembly, e.g. a module) and its children (e.g. a sensor that is part of the module) which are permanently attached.
Therefore, the database is planned to prohibit shipments of items which are currently a child of an assembly to a new location, as child components are assumed to be permanently attached to their assembly parent.
If you want to ship an item that is currently part of an assembly, it needs to be disassembled first (in the database sense) - only disassembled children can be shipped.
On the other hand: if an assembly is shipped, all components included in that assembly are assumed to move with it, therefore, in order to ship a full assembly with all its components, only the assembly or parent component has to be shipped.