Project

General

Profile

Actions

Feature #263

open

Support alternate prefix for reading database

Added by Ole Hansen about 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
8.00 h
Responsible:

Description

If a detector's database is identical, or maybe only slightly different, from that of another detector, it would be very convenient to be able to tell the detector to use that other detector's database instead of looking for its own copy. This could be implemented as a fallback mechanism. If a database key with the actual prefix isn't found, and an alternate prefix is given, then try reading the key again with that alternate prefix.

This is particularly interesting for doing comparison studies. Either there are modules with different algorithms that use the same (or largely identical) database info, or one wants to try out variations of a small number of parameters while keeping the rest of the database the same. Currently, one has to make a complete copy of each database file to accomplish that. That's somewhat wasteful and cumbersome, but more importantly, it makes it hard to see the differences.

No data to display

Actions

Also available in: Atom PDF