<<< This feature and this topic are under construction and may change without notice >>>


Reported Issues:


Category - File:

  • Issue: Duplicate filenames found in more than one folder: {count, list}
    1. Details: The same filename was found in more than one folder
    2. Ramifications: Complicates data management (need to remember to update all occurrences of file), inflates size of database
    3. Resolution: Consider restructuring folder structure to eliminate (or minimize) occurrence of duplicate files in different folders in the same database

 

Category - Keywords:

  • Issue: Inconsistent Keyword description - [MANUFAC]: {count}
    1. Details: Self-explanatory
    2. Ramifications: Shouldn’t your company name be the same across all of your products in the same database?
    3. Resolution: Using Photometric Power Tools to set global description for [MANUFAC]

 

  • Issue: Missing Keyword - [MANUFAC], [LUMCAT], [ISSUEDATE], [TESTLAB], [TEST], [TESTDATE]: {count}
    1. Details: Indicated Keyword should be in all files
    2. Ramifications: May cause parsing and/or scheduling issues
    3. Resolution: Use Photometric Power Tools to add indicated Keyword to files where it is missing

 

  • Issue: Blank Keyword description - [MANUFAC], [LUMCAT], [ISSUEDATE], [TESTLAB], [TEST], [TESTDATE]: {count}
    1. Details: Indicated Keyword was found but with no description
    2. Ramifications: May cause parsing and/or scheduling issues
    3. Resolution: Use Photometric Power Tools to find and add description for indicated Keyword

 

  • Issue: More than one occurrence of the same Keyword in same file - [MANUFAC], [LUMCAT], [ISSUEDATE], [TESTLAB], [TEST], [TESTDATE]: {count, list}
    1. Details: More than one occurrence of the indicated Keyword was found in the indicated file(s)
    2. Ramifications: Only the first or last occurrence will be used. May cause scheduling issues (which description should be used?)
    3. Resolution: Edit indicated files (using Photometric Power Tools or other editing tool) and remove duplicate Keywords

 

  • Issue: Invalid or unrecognized date format - [ISSUEDATE], [TESTDATE]: {count, list}
    1. Details: Unable to parse date. Note: This may vary by regional settings (i.e. valid date formats in one region may invalid in other regions)
    2. Ramifications: Unable to parse date which may cause issues when checking dates or scheduling
    3. Resolution: Edit indicated files and replace invalid date format. Recommend using a universal date format (e.g. dd-MMM-yyyy)

 

  • Issue: Date > {threshold} yrs. old - [ISSUEDATE], [TESTDATE]: {count}
    1. Details: Date for indicated Keyword is greater than threshold
    2. Ramifications: File and/or product may be out of date or no longer available (discontinued)
    3. Resolution: Find and check files using PPT. Update date as needed, remove discontinued products from database

 

  • Issue: Unsupported Keyword(s) found: {count, list}
    1. Details: Non-user defined Keywords were found that are not on the approved LM-63 Keyword list
    2. Ramifications: Most likely ignored by file parsers
    3. Resolution: Change to User Defined Keyword (prefix Keyword with underscore)
    4. Example: [FACTORED] --> [_FACTORED]

 

Category - Numeric Data:

  • Issue: Invalid Watts value (<= 0): {count}
    1. Details:
    2. Ramifications:
    3. Resolution:

 

  • Issue: Suspicious Watts value (= 1): {count}
    1. Details:
    2. Ramifications:
    3. Resolution:

 

  • Issue: Luminous Shape – Point: {count}
    1. Details: Luminous Dimensions are not defined (all zero)
    2. Ramifications: Unable to properly size luminous area which may result in inaccurate calculations. In addition, unable to calculate Luminance Data, UGR and properly select and size associated symbol
    3. Resolution: Use PPT to find Shape = Point, edited luminous dimensions as needed

 

  • Issue: Luminous Shape – Unknown or Unsupported: {count}
    1. Details: Specified Luminous Dimensions are invalid or result in a shape not supported by AGi32
    2. Ramifications: Unable to properly size luminous area which may result in inaccurate calculations. In addition, unable to calculate Luminance Data, UGR and properly select and size associated symbol
    3. Resolution: Use PPT to find Shape = Other, edit luminous dimensions as needed

 

  • Issue: Luminous Very large Luminous Dimensions (> {threshold}): {count}
    1. Details: Luminous Dimension exceed indicated threshold. May be the result of specifying dimensions in the incorrect units (e.g. inches instead of feet)
    2. Ramifications: Invalid luminous area which may result in inaccurate calculations
    3. Resolution: Use PPT to locate files, edit luminous dimensions are necessary

 

Category - Photometric Web Angle Set:

  • Issue: Large horizontal angular increment (> {threshold}-degrees)l: count}
    1. Details:
    2. Ramifications: May indicate in adequate exploration to properly describe the photometric distribution
    3. Resolution: Luminaire may need to be retested
    4. Example:

 

  • Issue: Large vertical angular increment (> {threshold}-degrees): {count}
    1. Details:
    2. Ramifications: May indicate in adequate exploration to properly describe the photometric distribution
    3. Resolution: Luminaire may need to be rested
    4. Example:


  • Issue: No uplight and candela at 90-degrees vertical is > 0: {count}
    1. Details: Indicates there is light at 90-degress (> 0) but there is no data about 90-degrees vertical (data was truncated?)
    2. Ramifications: Unable to calculate BUG
    3. Resolution: Use PPT to find and check files, may need to retested to include data 90-180 vertical
    4. Example:


  • Issue: Nearly symmetric distribution reported as asymmetrical: {count, list}
    1. Details: - House side vs. street side lumens < = {threshold} different
    2. Ramifications: May indicate candela rounding issue or luminaire not properly leveled when tested (slight tilted)
    3. Resolution: Check file, if supposed to be symmetrical may need to test
    4. Example:

 

Category - Candela Values:

  • Issue: High precision candela values (> {threshold} decimals): {count}
    1. Details: High precision candela could be the result of factoring or sloppy reporting. Candela values should be rounded when published
    2. Ramifications: Unneeded precision unnecessarily inflates the size of the file
    3. Resolution: Use PPT to round candela values
    4. Example:

 

Category - Calculated Metrics:

  • Issue: Efficiency too high (> {threshold}%): {count}
    1. Details: Generally, indicates an incorrectly factored file
    2. Ramifications: Calculations using this file are most likely invalid
    3. Resolution: Check file
    4. Example:

 

  • Issue: Efficiency suspiciously high (> {threshold}): {count}
    1. Details: May indicate a factoring issue (incorrectly factored) or a relative photometric file that should actually be absolute
    2. Ramifications: Calculations using this file may not be valid
    3. Resolution:
    4. Example:

 

  • Issue: Efficiency suspiciously high for Relative Photometry (> {threshold}): {count}
    1. Details: May indicate a factoring issue (incorrectly factored) or a relative photometric file that should actually be absolute
    2. Ramifications: Calculations using this file may not be valid
    3. Resolution:
    4. Example: