Hi Tao Hu,
hypercube expects envi header file to be in form of sample header file specified in this following link: https://www.l3harrisgeospatial.com/docs/enviheaderfiles.html.
hypercube expects "ENVI" characters to be present in first line of header file and have "=" to be the delimiter to seperate the key name and value pairs. hypercube is returning error since the sample header file you mentioned doesn't adhere to these presumptions.
We will look into the sample header file you have provided to check whether we can support it too. As of now, there are no alternatives apart from creating hypercube object with numeric array and wavelength as you have already done.
The data in the file for ENVI image data will be interleaved with bil, bip, and bsq encoding. Interleave will therefore be present in the file and be utilised to read data back, although it is not required for numeric arrays.
We are hard coding because the input numeric array (MxNxC) doesn't require interleave and it is in the form of band by band by channel, which reads as band by sequential.
You can set the "interleave" while writing the data back to the envi file using "enviwrite".
