• 2 Posts
  • 118 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle


  • I daily drive Fedora and if I had to guess, it’s because you need to manually enable non free software repos and features. If you don’t know what to look for, you can easily get frustrated by things like poor hardware acceleration in browsers (due to some codecs being nonfree and hence not available OOTB) and worse driver availability. IIRC you need to manually add the repos, you can’t just toggle something in settings.

    Other distros tend to bundle these things (or give you a direct toggle).





  • I work in an area adjacent to autonomous vehicles, and the primary reason has to do with data availability and stability of terrain. In the woods you’re naturally going to have worse coverage of typical behaviors just because the set of observations is much wider (“anomalies” are more common). The terrain being less maintained also makes planning and perception much more critical. So in some sense, cities are ideal.

    Some companies are specifically targeting offs road AVs, but as you can guess the primary use cases are going to be military.






  • Unfortunately proprietary professional software suites are still usually better than their FOSS counterparts. For instance Altium Designer vs KiCAD for ECAD, and Solidworks vs FreeCAD. That’s not to say the open source tools are bad. I use them myself all the time. But the proprietary tools usually are more robust (for instance, it is fairly easy to break models in FreeCAD if you aren’t careful) and have better workflows for creating really complex designs.

    I’ll also add that Lightroom is still better than Darktable and RawTherapee for me. Both of the open source options are still good, but Lightroom has better denoising in my experience. It also is better at supporting new cameras and lenses compared to the open source options.

    With time I’m sure the open source solutions will improve and catch up to the proprietary ones. KiCAD and FreeCAD are already good enough for my needs, but that may not have been true if I were working on very complex projects.


  • Cute cat! Nevermore and Bentobox are two super popular ones.

    Since you’re running an E3 V2, first make sure you’ve replaced the hotend with an all-metal design. The stock hotend has the PTFE tube routed all the way into the hotend, which is fine for low temp materials like PLA, but can result in off-gassing at higher temperatures such as those used by ASA and some variants of PETG. The PTFE particles are almost certainly not good to breathe in during the long term, and can even be deadly to certain animals such as birds at small quantities.



  • Yeah, I agree. In the photo I didn’t see an enclosure so I said PETG is fine for this application. With an enclosure you’d really want to use ABS/ASA, though PETG could work in a pinch.

    I also agree that an enclosure (combined with a filter) is a good idea. I think people tend to undersell the potential dangers from 3D printing, especially for people with animals in the home.




  • KingRandomGuy@lemmy.worldto3DPrinting@lemmy.worldEnder 3 V2 damage?
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    3 months ago

    PETG will almost certainly be fine. Just use lots of walls (6 walls, maybe 30% infill). PETG’s heat resistance is more than good enough for a non-enclosed printer. Prusa has used PETG for their printer parts for a very long time without issues.

    Heat isn’t the issue to worry about IMO. The bigger issue is creep/cold flowing, which is permanent deformation that results even from relatively light, sustained loads. PLA has very poor creep resistance unless annealed, but PETG is a quite a bit better. ABS/ASA would be even better but they’re much more of a headache to print.


  • I agree that pickle works well for storing arbitrary metadata, but my main gripe is that it isn’t like there’s an exact standard for how the metadata should be formatted. For FITS, for example, there are keywords for metadata such as the row order, CFA matrices, etc. that all FITS processing and displaying programs need to follow to properly read the image. So to make working with multi-spectral data easier, it’d definitely be helpful to have a standard set of keywords and encoding format.

    It would be interesting to see if photo editing software will pick up multichannel JPEG. As of right now there are very few sources of multi-spectral imagery for consumers, so I’m not sure what the target use case would be though. The closest thing I can think of is narrowband imaging in astrophotography, but normally you process those in dedicated astronomy software (i.e. Siril, PixInsight), though you can also re-combine different wavelengths in traditional image editors.

    I’ll also add that HDF5 and Zarr are good options to store arrays in Python if standardized metadata isn’t a big deal. Both of them have the benefit of user-specified chunk sizes, so they work well for tasks like ML where you may have random accesses.


  • I guess part of the reason is to have a standardized method for multi and hyper spectral images, especially for storing things like metadata. Simply storing a numpy array may not be ideal if you don’t keep metadata on what is being stored and in what order (i.e. axis order, what channel corresponds to each frequency band, etc.). Plus it seems like they extend lossy compression to this modality which could be useful for some circumstances (though for scientific use you’d probably want lossless).

    If compression isn’t the concern, certainly other formats could work to store metadata in a standardized way. FITS, the image format used in astronomy, comes to mind.