Get email delivery of the Cadence blog featured here
You're a designer working on an Allegro System Capture project and you clicked on Place – Add Component some time back, but here's what you've been staring at for a while:
You're seeing this because when you clicked Place - Add Component, System Capture automatically started indexing the libraries to speed up future part searches. If you have very large, non-Allegro EDM managed libraries, it can take a while to complete the indexing.
Admins, do your designers often search for parts when creating Allegro System Capture projects? Yes. Do they work with large ECAD libraries? Yes. Do you work with Allegro EDM Library Manager? No. Well, in that case, you could improve your end users’ experience in two ways:
Here’s an example of a central index path:START_COMPBROWSERcentral_index_path 'D:/central_indexed_db'END_COMPBROWSER
If you add or remove libraries by manually editing $CDS_SITE/cdssetup/cds.lib or through the user interface (Edit – Project Preferences), you'll need to re-index the database by running indexer.bat again. You can simplify your life by configuring this task as a Cron job (so that all changes are automatically and periodically re-indexed) or manually run indexer.bat whenever your libraries are updated. The updated indexed data is automatically available in part searches in System Capture designs.
Does System Capture need a lot of memory to load the indexed database? Hmm…it depends.
Not the case here, but…
System Capture with CENTRAL_INDEX_PATH + Allegro EDM server
In fact, because System Capture fetches only required data from the EDM server and the designer's machine has no library data loaded on it, this consumes the least memory.
So, there you go…happy and faster searching!