powered by CADENAS

Manual

Manual

5.8.2.1.15.15.  Resolve check

Use case:

In order for value ranges to be considered during search and the single values to be found, they have to be indexed.

For catalogs without value ranges there is no need for indexing.

If the number of possible combinations resulting from the value ranges is too big, no indexing will take place, but instead a ReverseConfig is used, which enables finding of value range values as well.

The Resolve check will check, if catalogs are resolvable in Lucine index or if a ReverseConfig is needed.

The result of the analysis is displayed in a dialog box.

Example on Level A

Example on Level A

Example on Level C

Example on Level C

The following parameters are numbered. (Not all have to exist always.)

  • Amount of all projects:

  • Amount simple projects: Projects without value ranges

  • Amount complex projects: Projects with value ranges

    [Note] Note

    Projects already equipped with a pnoreverse.cfg are not listed here anymore.

  • Amount projects over limit: These projects show the value <not resolvable> in the Excel file.

    These projects have to be resolved via pnoreverse.cfg. On this see ???.

  • Amount projects with flag: The check only considers existing projects with flag.

    Flag means, that these projects may be resolved in the index. Projects, which are resolved via pnoreverse.cfg, will not display here.

    A catalog, which has not been edited yet with the Resolve check normally will show "0" here (except settings have been made manually).

  • Amount projects with reverse: A catalog, which has not been edited yet with the Resolve check, normally will show "0" here. Counting will take place, if there is a <projectname>_pnoreverse.cfg available yet.

  • Amount of all lines:

  • Amount simple lines:

  • Amount complex lines:

  • Suggestion: The statement of percentage concerns the ratio of Amount projects over limit to Amount complex projects.

    Example:

    33,33% of the projects couldn't be resolved. Compare above Fig. „Example on Level C“.

Call/Process:

  1. Right-click on a catalog or a directory -> Automation -> Resolve check

  2. After a few seconds / minutes the result is displayed.

Function:

The plugin automatically sets the key REVERSEANALYSIS in the single projects (internal saving of analysis data for the display in the dialog box, no display in GUI).

REVERSEANALYSIS=<GEOMDATE zur Zeit des Laufs>; <visible rows>; <resolved number>;

Furthermore the following entry is automatically set in the dir.prj of catalog.

REVERSEANALYSIS=<Zeit des Laufs>

From the dialog of analysis result the key VARSEARCHRESOLVEORDERNO can automatically be set for the catalog and all projects by clicking Yes.

The respective setting option in the GUI is found under PARTproject -> Edit project -> tabbed page General -> Search index creation -> Index order numbers dependent on value ranges. Details on this setting can be found under Section 5.9.2.14, “ Search index creation ”.

Index order numbers dependent on value ranges

Index order numbers dependent on value ranges

Furthermore the flag for pnoreverse can be set from the analysis dialog.

Following cases can be differentiated:

  • Level A: Display that nothing has to be done.

    May be the complete catalog only contains simple projects, meaning projects which do not contain yellow fields (value range fields) -> Standard Lucene

    Level A - Nothing to do here. The catalog fits completely in the lucene index.

    Level A - Nothing to do here. The catalog fits completely in the lucene index.

    It is also possible that the catalog contains projects which cannot be mapped by Lucine index, but these are already mapped by respective <projectname>_pnoreverse.cfg.

    Level A - Nothing to do here. The catalog fits completely in the lucene index.

    Level A - Nothing to do here. The catalog fits completely in the lucene index.

  • Level B: Complex projects, which means that yellow fields exist, but that they can be completely resolved with less than 25000 rows per project. So for the respective catalog no ReverseConfigs have to be used.

    • B1: The catalog remains under 50000 rows -> With a click on Yes, "Resolve" is set for the whole catalog (key VARSEARCHRESOLVEORDERNO).

      Catalog setting: Index order numbers dependent on value ranges = Yes

      Catalog setting: Index order numbers dependent on value ranges = Yes

      [Note] Note

      An Excel file with a listing of all projects is opened only due to informative reasons. File changes have no relevance and are not used.

    • B2: The catalog (= resolvable projects) is over 50000 rows. -> Script opens Excel file (or Notepad, according to system settings) with a listing of all projects.

      • Projects can explicitely be set on 1 by user input

        Example Excel row:

        E:\data\23d-libs\catalog\parts\m\mas\mas_bk_sbl_tab.prj;"6";"<not resolveable>";"0"
        

        E:\data\23d-libs\catalog\parts\m\mas\mas_bk_sbl_tab.prj;"6";"<not resolveable>";"1"
        

      • Projects can be removed from Excel file, in order to reach a maximum of 50000 rows.

      Once saving the Excel/Notepad file, the dialog box Information is opened asking whether you want to apply settings of the CSV file.

      Once confirming with Yes, the settings are applied.

  • Level C: Yellow fields can be resolved partly, but the catalog has also projects which cannot be resolved with less than 25000 rows, so for these a <projectname>_pnoreverse.cfg is needed.

    • C1: Resolvable projects altogether stay under 50000 rows -> With a click on Yes "Resolve" is set for the whole catalog (key VARSEARCHRESOLVEORDERNO).

      [Note] Note

      An Excel file with a listing of all projects is opened only due to informative reasons. File changes have no relevance and are not used.

      Example:

      • Amount complex projects: 3

        => Excel opens with 3 rows (rows displayed in Excel generally concern complex projects).

        The Excel file shows 4 parameters, separated by semicolon:

        • Path (PATH)

        • Number of rows (RANGES)

        • Number of resolved rows (AMOUNT)

        • Resolve Flag: (RESOLVE) Default value is "0". Here, "1" must be set, if in the project, the key VARSEARCHRESOLVEORDERNO shall get the value "1".

        When clicking on Yes, in the dialog box of analysis results, the key VARSEARCHRESOLVEORDERNO is set to "1" on catalog level. Resolvable projects pull the catalog setting.

      • Amount projects over limit: 1

        You can recognize these rows by the parameter <not resolvable>.

        => For this not-resolvable project a <projectname>_pnoreverse.cfg has to be created and the key VARSEARCHRESOLVEORDERNO is set to "0".

    • C2: Resolvable projects altogether exceed 50000 rows -> Script opens Excel file with a listing of all projects.

      Projects can explicitely be set on "1" by user input.

      Projects can be removed from the Excel file, in order to reach a maximum of less than 50000 rows. If this value exceeds, resolving has to be achieved via pnoreverse.cfg. On this see Section 5.8.2.1.15.16, “ Reverse TypeCode Rule Editor ”.

      Once saving in Excel, the dialog box Information is opened asking whether you want to apply settings of the CSV file.

      Once confirming with Yes, the settings are applied.

  • Level D: No project is resolvable under 25000 rows. -> Recommendation: Perform reverse resolving via config (pnoreverse.cfg). See Section 5.8.2.1.15.16, “ Reverse TypeCode Rule Editor ”. No flags are set.

[Note] Note

Invisible (red) projects can also be indexed. For this there is the key SEARCHINDEX=ON in the project file.

These projects are also considered from the Resolve check.