Stories

ASK: HN Help and Forward Advice, Ideas: New Lossless cmpr MRT/CT, Astro

Article news.ycombinator.com

ASK: HN Help and Forward Advice, Ideas: New Lossless cmpr MRT/CT, Astro

Hey HN,

at first, i'm not from that subject field so I dont know what to do. I'm an ordinary engeneer with basics and unorthodox thinking. I used Claude to help me implement. Its a process of several months and bazills of millions of tokens of work. I can't show or disclose, begging for your understanding.

I can't beat WEBP lossless on kodak test suite, YET; But I'm like 5% worser on RGBa. CMYK's similar. Here, the advantage is me being 5-15x faster as WEBP / other lossless codecs. Not yet fully confirmed, but promissing results WEBP will be knocked too. My lossy compression is better than JPEG sometimes, but always ~10++ times faster. Very big building field right now.

The figures are very promissing on lossless video. On cpu cycles beating every SOTA methods by being upto 15x faster or so. Possible path. My lossy shows better sharpness and details in (very) fast moving scenes (1080p, 2k, 4k incl. hdr), while being only ~5-10% bigger than heif and avc, and others with comperable compression params. May be is resolved in x-xx weeks.

→ noticed, my lossless works better as SOTA (JPEG LS, JPEG 2000 and JPEG XL, each lossless mode) on medical imaging / DICOM, voluminetric medical/scientific data, handles pixel bitdepths >32bit; >32000x32000px (jpeg didnt even consume). It seems to scale res/depth without issues. Runs on data from various MRT/CT Imagers and formats found for download show ~15%-50% percent better compression as SOTA/DICOM, at a fraction of cycles. Some results:

CT volumes, ratio and (encode / decode seconds)

- pancreas, 185 slices → 3.26 (0.7 / 0.6) │ JPEG-LS: 2.69 (2.3 / 1.8) │ JPEG 2000: 2.71 (10.6 / 8.5) │ FFV1: 2.70

- COVID chest, 2464 slices → 4.48 (10.0 / 8.6) │ JPEG-LS: 3.30 (24.6 / 18.9) │ JPEG 2000: 3.12 (129 / 101) │ FFV1: 3.21

- Colonography, 950 slices → 2.79, was 2.59 │ JPEG-LS: 2.73 (10.9 / 8.8) │ JPEG 2000: 2.61 (55.6 / 44.2) │ FFV1: 2.99

- LIDC lung, 764 slices, 12-bit → 2.67 (3.1 / 2.8) │ JPEG-LS: 2.40 (9.9 / 7.7) │ JPEG 2000: 2.40 (46.1 / 37.9) │ FFV1: 2.37

- TCGA kidney, 820 slices → 3.31 (3.3 / 2.9) │ JPEG-LS: 2.87 (9.2 / 7.1) │ JPEG 2000: 2.74 (48.1 / 37.3) │ FFV1: 2.80

MR and SAR data is also a possible play field with some prommissing results I've already seen.

So, as everyone too, i want $$$. I decided to walk my own way after being fired in 2 mins two years ago and I dont have much financial reserves left, without getting income atm. Can't start employment; Need & Want to fight with Claude 23h/7d instead on other ideas I'm working on since years. Need MONEY!! So, if you would be me. Open Sourcing the algorithm is bread-less and doesn't pay my/your bills.

I'm seeking Advice or Ideas on how would you approach it, if you were me - with max profit in the head (.. but still do good!).

The actual and future storage/memory crisis opens up a lever. My approach puts together: storage AND compute can both be siginificantly reduced.

- AWS health services, google health and some other smaller cloud service providers

- Medical imaging device producers (mrt/ct) saving on cpu and memory

- Physicians using SaaS for storage/viewing

- Astro/Scientific imaging and processing

- Possible space/SAR/satelite imaging/data, not giving up on it yet.

But how to approach?? If you give it to x, then y will need it too for processing x's data. This gives a conflict in interest. Interest is profit max. What could end up as a strategy? How to find someone to pitch? Selling? Licensing? Other models? Patenting may not work / doesn't use patented methods.

Appreciate any answer and 'thank you' to everyone reading. If I dont respond to your comment, think of me saying 'thank you' while bowing very deeply, weaving my hat. This post is not meant to let others do my work, its a scream for direction - kind of desperate & blind

Discussion 0 comments · 1 points · theGeatZhopa · 15h
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    New collection

    Delete this collection?

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Privacy policy · Terms of use

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    ]
    Read the next story in the same article-reader applet. Back returns to the previous story.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Next story link reads on down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.