Error messages are those that appear when no plot is created. These indicate issues that must be resolved before the data can be plotted. If an error message appears that is not included in this document or is null, please contact horticulture@designlights.org.

Warning messages are those that appear when plots are generated. This indicates that there may be an issue with the TM-33 file that will impact qualification, but none of these issues affect the plot that is produced. 

---

Errors

Missing Elements:

Output Message	Meaning/How to Correct the Error
“[Element Name] is required for Hort V3.0 submission but was not found in the correct location in the submitted file. This must be resolved before photometric images can be created.”	A required element is missing from the submitted document. This warning can also appear when an element name is misspelled, or an element is nested in the incorrect location. Correct example: Incorrect example: The above image is incorrect according to TM-33-18, because MinWavelength and MaxWavelength elements are nested inside the PhotonIntensity element. In both cases, there will also be a warning stating that there is an extra element. To resolve this issue please add the specified element to the correct location in the document. Refer to the sample TM-33 document as a reference for all required elements and their specified locations.
“EmitterName is required for Hort V3.0 submission for products with multiple emitters but was not found in the correct location in the submitted file. This must be resolved before photometric images can be created.”	Multiple EmitterSpectral elements are present, and one or more of them does not contain the EmitterName element.   To resolve this issue, ensure that an EmitterName element is present within each EmitterSpectral element, and that the EmitterName text describes the emitter, channel, or condition that the data represents.

SpectralData Errors:

Output Message	Meaning/How to Correct the Error
“Within the Emitter/SpectralData element, the NumberWavelength value must match the total number of wavelength measurements. This must be resolved before photometric images can be created.”	The number of PwrData elements is different from the NumberWavelength value. To correct this issue, change the NumberWavelength value to reflect the number of PwrData elements present in the EmitterSpectral element.
“The minimum wavelength value within the SpectralData/PwrData elements must not be greater than 400nm. This must be resolved before photometric images can be created.”	The smallest wavelength value is greater than 400nm. To correct this issue, please include data that ranges down to 400nm.
“The maximum wavelength value within the Spectral Data/PwrData elements must not be less than 800nm. This must be resolved before photometric images can be created.”	The largest wavelength value is less than 800nm. To correct this issue, please include data that ranges up to 800nm.
“Within the SpectralData/PwrData elements, the wavelength increment must not be larger than 5nm. This must be resolved before photometric images can be created.”	The wavelengths within the PwrData elements have an increment larger than 5nm. To correct this issue, please ensure all wavelengths are at most 5nm apart. The below example would not be accepted, because adjacent wavelengths are 10nm apart.
“The PwrData and/or NumberWavelength elements within the Emitter/SpectralData/EmitterSpectral element were not detected. Please check that all required elements are present and that there are no typos in the element names. This must be resolved before photometric images can be created.”	The NumberWavelength element or all PwrData elements are missing from the EmitterSpectral section. This error may also appear if these element names are misspelled as shown here. To correct this issue, please ensure that NumberWavelength and PwrData elements are present in the correct location in the file, and that they are spelled correctly.

PhotonData Errors:

Output Message	Meaning/How to Correct the Error
“Within the Emitter/PhotonData element, the NumberMeasured value must equal the number of horizontal angles multiplied by the number of vertical angles. This must be resolved before photometric images can be created.”	The NumberHorz value multiplied by the NumberVert value does not equal the NumberMeasured value. To correct this issue, ensure that the NumberHorz, NumberVert, and NumberMeasured element values accurately reflect the number of data points in the file.
“Within the Emitter/PhotonData element, the NumberMeasured value must equal the total number of photon intensity measurements. This must be resolved before photometric images can be created.”	The number of IntData elements is different from the NumberMeasured value. To correct this issue, change the NumberMeasured value to reflect the number of IntData elements present in the PhotonIntensity element.
“Within the Photon Data element, the horizontal angle increment must not be larger than 22.5 degrees. This must be resolved before photometric images can be created.”	The horizontal angles in the file have an increment greater than 22.5 degrees. To correct this issue, please ensure all horizontal angles are at most 22.5 degrees apart.
“Within the Emitter/PhotonData element, the vertical angle increment must not be larger than 5 degrees. This must be resolved before photometric images can be created.”	The vertical angles in the file have an increment greater than 5 degrees. To correct this issue, please ensure all vertical angles are at most 5 degrees apart.
“Within the Emitter/PhotonData element, the NumberHor value must equal the total number of horizontal angles present. This must be resolved before photometric images can be created.”	The number of distinct horizontal angles within the IntData elements is different from the NumberHor value. To correct this issue, change the NumberHor value to reflect the number of distinct horizontal angles present in the document.
“Within the Emitter/PhotonData element, the NumberVert value must equal the total number of vertical angles present. This must be resolved before photometric images can be created.”	The number of distinct vertical angles within the IntData elements is different from the NumberVert value. To correct this issue, change the NumberVert value to reflect the number of distinct vertical angles present in the document.
“Within the Emitter/PhotonData element, vertical angles must be consistent across all horizontal angles. This must be resolved before photometric images can be created.”	One set of vertical angles is different from another. For example, this error would appear if the vertical angles at h=0 had an increment of 5 degrees and the vertical angles at h=90 have an increment of 2.5 degrees. To correct this issue, ensure that the vertical angles are the same at each horizontal angle.
“Vertical angle at 90 degrees was not found. Update file to include intensity data at v=90 degrees.”	Data at the vertical angle 90 degrees was not found in the submitted document. To correct this issue, please ensure that the data set includes v=90.
“The range of vertical angles is not valid. The largest vertical angle must be 90 degrees or 180 degrees. This must be resolved before a plot can be created.”	The largest vertical angle in the document is not equal to 90 or 180 degrees. Acceptable vertical angle ranges include 0-90 degrees, 0-180 degrees, or 90-180 degrees.
“Within PhotonData, all photon intensity values at nadir (vertical angle: 0 degrees) must be the same. This must be resolved before photometric images can be created.”	The IntData values at v=0 have a difference greater than 1µmol/s*sr. To ensure quality data, the DLC requires that all measurements at v=0 are within 1µmol/s*sr of each other.
“Within PhotonData, all photon intensity values at zenith (vertical angle: 180 degrees) must be the same. This must be resolved before photometric images can be created.”	The IntData values at v=180 have a difference greater than 1µmol/s*sr. To ensure quality data, the DLC requires that all measurements at v=180 are within 1µmol/s*sr of each other.
“Multiple PhotonData elements were detected within a single Emitter element. Each PhotonData element must be contained in a unique Emitter element. This must be resolved before photometric images can be created.”	Multiple PhotonData elements are present within a single Emitter element. TM-33-18 requires that each Emitter element must contain only one PhotonData element with PPID data.   To resolve this issue, create a new Emitter element for each set of PPID data you would like to include, so that there are multiple Emitter elements, and each one contains no more than one PhotonData element.

Element Value Errors:

Output Message	Meaning/How to Correct the Error
“The luminaire housing length must not be equal to zero, contain units, or be blank. This must be resolved before photometric images can be created.”	There is an issue with the Length value within the Dimensions element. This warning will appear when (1) The length is equal to zero (2) The length is blank (3) The length value contains a character that is not a number To correct this issue, please ensure that all dimension values are non-zero numbers.
“The luminaire housing width must not be equal to zero, contain units, or be blank. This must be resolved before photometric images can be created.”	There is an issue with the Width value within the Dimensions element. This warning will appear when (1) The width is equal to zero (2) The width is blank (3) The width value contains a character that is not a number To correct this issue, please ensure that all dimension values are non-zero numbers.
“The luminaire housing height must not be equal to zero, contain units, or be blank. This must be resolved before photometric images can be created.”	There is an issue with the Height value within the Dimensions element. This warning will appear when (1) The height is equal to zero (2) The height is blank (3) The height value contains a character that is not a number To correct this issue, please ensure that all dimension values are non-zero numbers.
“The number of emitters (NumEmitter element) must not be equal to zero, contain units, or be blank. This must be resolved before photometric images can be created.”	There is an issue with the NumEmitter value within the Luminaire element. This warning will appear when (1) The NumEmitter is equal to zero (2) The NumEmitter is blank (3) The NumEmitter value contains a character that is not a number To correct this issue, please ensure that the NumEmitter element contains a non-zero number.
“Emitter/DataGeneration/AngleInterpolation must be True or False. This must be resolved before photometric images can be created.”	The AngleInterpolation value is something other than “True” or “False”. To correct this issue, please replace the AngleInterpolation value with “True” or “False”.
“The Emitter/PhotonData/MinWavelength element value must be 400nm. This must be resolved before photometric images can be created.”	The MinWavelength value within the PhotonData element is something other than 400. To correct this issue please ensure that the measurement includes wavelengths that range from 400 to 700nm, and that there are no units or other characters included in the MinWavelength value.
“The Emitter/PhotonData/MaxWavelength element value must be 700nm. This must be resolved before photometric images can be created.”	The MaxWavelength value within the PhotonData element is something other than 700. To correct this issue please ensure that the measurement includes wavelengths that range from 400 to 700nm, and that there are no units or other characters included in the MaxWavelength value.
“Within the CustomData element, the Name element must equal ‘Radiant Power to PPF Scalar Multiplier’. This must be resolved before photometric images can be created.”	The Name value within the CustomData element is something other than “Radiant Power to PPF Scalar Multiplier.” To correct this issue, change the Name value to match this wording.
“Within the Luminaire element, the NumEmitter value must match the number of Emitter elements present in the document. This must be resolved before photometric images can be created.”	The text value of the NumEmitter element does not match the number of Emitter elements present in the document.   To resolve this issue, adjust the value of the NumEmitter element accordingly.

General Errors:

Output Message	Meaning/How to Correct the Error
“The uploaded file does not comply with the ANSI/IES TM-33-2018 .xml document format and therefore cannot be used with this pre-submission tool. Please refer to the TM standard and DLC supplemental documentation for more information on how to format your .xml document.”	(1) The file extension of the submitted document is something other than .xml. To correct this issue, please ensure that the submitted document is in .xml format and complies with ANSI/IES TM-33-2018, or (2) An error in the XML formatting is preventing the submitted document from being parsed. This can be caused by a variety of things. Most commonly, this occurs when the opening end of an element does not match the closing end or one of the ends is missing Below is an example of proper formatting for a single element. If attributes are included, they must be formatted as below. Standalone element tags in the following format are also acceptable but cannot be followed by a closing tag. The element name must be spelled the same on both sides, and the formatting cannot deviate from that of the examples shown above (e.g. with missing brackets or quotation marks, or extra backslashes), or the file will not be parsed, because the code cannot recognize where an element begins and ends.   Certain programs such as Visual Studio will put a red line under any formatting issues, as shown in the examples above, which can make them easier to identify.   For further information, please contact horticulture@designlights.org.
“Something went wrong, please review your submitted document and upload again.”	An unknown error is preventing the submitted document from being processed. If you see this message, please contact horticulture@designlights.org.

Warnings

Missing and Extra Elements:

Output Message	Meaning/How to Correct the Error
“[Element Name] is not a valid element specified by TM-33. This may need to be corrected before the product can be qualified.”	An element is present in the submitted XML document that is not valid according to TM-33-18. This warning can also appear when an element name is misspelled, or an element is nested in the incorrect location. Correct example: Incorrect example: The above image is incorrect according to TM-33-18, because MinWavelength and MaxWavelength elements are nested inside the PhotonIntensity element.   In both cases, there will also be an error stating that the element is missing from the correct location. To correct this issue, please either remove the specified element from the document, or ensure that all elements are in the correct location.
“The CustomData/UniqueIdentifier element is missing. This may need to be corrected before the product can be qualified.”	The UniqueIdentifier element is not present within the CustomData section of the submitted document or contains no value. To address this issue, please ensure a Universally Unique Identifier is present in the CustomData section.
“The submitted file does not contain the PhotonData element, and therefore the Photosynthetic Photon Intensity Distribution cannot be plotted. This is allowed, but the data must be provided in a separate TM-33 .xml document for the product to be qualified.”	The submitted document does not contain either the PhotonData element or the PhotonIntensity element in the correct location, but the SpectralData SPD can still be plotted. This is a partial document, and is accepted by the tool, but the PhotonData must be provided in a separate document in order for the product to qualify.   If this is not the intention, please ensure that the PhotonData section of the submitted document is formatted correctly according to TM-33-18, and that spelling is correct.
“The submitted file does not contain the SpectralData element, and therefore Spectral Quantum Distribution cannot be plotted. This is allowed, but the data must be provided in a separate TM-33 .xml document for the product to be qualified.”	The submitted document does not contain either the SpectralData element or the EmitterSpectral element in the correct location, but the PhotonData PPID can still be plotted. This is a partial document, and is accepted by the tool, but the SpectralData must be provided in a separate document in order for the product to qualify.   If this is not the intention, please ensure that the SpectralData section of the submitted document is formatted correctly according to TM-33-18, and that spelling is correct.

Element Value Warnings:

Output Message	Meaning/How to Correct the Error
“Intensity scaling is not allowed. The Emitter/DataGeneration/IntensityScaling element must be False. This may need to be corrected before the product can be qualified.”	The IntensityScaling value is something other than “False.” To correct this issue, please use data that is not scaled, unless the product has been approved for intensity scaling.

Photon Data Warnings:

Output Message	Meaning/How to Correct the Error
“Photosynthetic photon flux in the downward direction was not detected. If this is not intended, please modify file prior to submission.”	Within the IntData elements, no vertical angles were detected between 0 and 90 degrees. This is accepted by the tool, but if the product is intended to emit PPF in the downward direction, please double check that the correct vertical angles are present in the submitted document.

Other

Output Message	Meaning/How to Correct the Error
“Null” Or any other output message not listed in this document	An unknown error has occurred. The “null” message most commonly appears when the first line of the xml file is missing: This prevents the program from recognizing the document as xml. Please refer to the downloadable sample TM-33 document on the Presubmission Tool page as a reference for formatting. Please contact horticulture@designlights.org with any questions.