Hacker News new | ask | show | jobs
by __mharrison__ 542 days ago
Hint. If your library is for creating images... Put an example image in the Readme.
2 comments

I tried to understand what this library does, but without image examples its impossible for me. The docs almost seem to be unhelpful on purpose. Look at the use case description: "The functionality of the SiaPy library has been implemented in various use cases, demonstrating its capabilities and potential applications. The library's functionality is not limited to these examples and can be extended to other applications as well."

Are we living in the dead Internet already where everything is meaningless AI garbage?

Spectral images are images where there are several sensors into one image (think visible and infrared/thermal for instance). A good example would be Altum Pt camera (https://ageagle.com/drone-sensors/altum-pt-camera)

Then, this library can be used for instance (their word) - Display images from two cameras. - Co-register cameras and compute the transformation from one camera's space to another. - Select regions in images for training machine learning (ML) models. - Perform image segmentation using a pre-trained ML model. - Convert radiance images to reflectance by utilizing a reference panel. - Display spectral signatures for in-depth analysis.

Yes I know, but this is still my free time and effort I am putting in. I will try to add additional examples over time, but for now this was everything I managed to do :) For now I was a solo developer, it would be much easier if anyone would help me out
It is a by-product of a research project, its main connection is "these things were useful to the author while working on spectral images".
As you figured, I gathered and refactured multitude of the code that I mainly used in my research project. However, this is still not to say that someone cant find it useful :) I make a ton of effort to at least document the api and write at least some parts of the docs ;)
Oh I didn't mean to sound dismissive, it's just easier to understand it as a toolkit defined mostly by necessity.
ok, just making sure that we are on the same page. Yeah, the inception was mostly organic, since in the last years I could not find a library that would enable me to easily do these things. Most of the code we use internally at the institute and I figured why not to share it with others. Maybe anyone will also get encouraged to help me with implementation of other useful features.
Thanks, I agree, the problem is that I was a solo developer for the enitre time and with me understanding it entirely it is easy to forget that peaople have a hard time understanding it. Will correct it ASAP. Thanks for the suggestion :)