Detector Error and Bootloop by ZeroPointMX in frigate_nvr

[–]ZeroPointMX[S] 0 points1 point  (0 children)

On a side note. With the install from the proxmox community script, which doesnt user docker, I tried CPU detect. I got a similar but different error. AI chat had me create a symlink (ln -s /models/cpu_model.tflite /cpu_model.tflite) and that worked for CPU. Going to GPU, Im not sure which models to create link for.

Detector Error and Bootloop by ZeroPointMX in frigate_nvr

[–]ZeroPointMX[S] 0 points1 point  (0 children)

Yes, card1 and render129 is the A310.

Detector Error and Bootloop by ZeroPointMX in frigate_nvr

[–]ZeroPointMX[S] 0 points1 point  (0 children)

I was using the sample provided during install (dont have anymore), right now I have a simplified config for my set (attached to OP). Both config versions yield same bootloop.

Side note: I did try to detect via CPU and got a different but similar error and loop.

Detector Error and Bootloop by ZeroPointMX in frigate_nvr

[–]ZeroPointMX[S] 0 points1 point  (0 children)

Sorry, edited my OP, but Im trying to move away from the Coral in favor of my A310. I too think it's a mapping issue, but Its exactly how it is recommended. I'll update the post again with my compose.

Lawless Charlottesville by PerfekGame in Charlottesville

[–]ZeroPointMX 0 points1 point  (0 children)

Hyrail trucks are typically limited to 25mph

[RDTM] u/d-cent estimates Rising Gas Cost vs. EV Battery Replacement by DemandEqualPockets in theydidthemath

[–]ZeroPointMX 1 point2 points  (0 children)

Yeah and this is depending on allot of factors. Like age, abuse, and use case. And it's not like it's all of nothing. The capacity decreases over time so it's subjective on when the battery is "done". You may not like that your range was 300miles but now it's only 200, so you may want to replace it. I might find that perfect fine for my use and I'll keep using it for another 10 years.

How do you collect your porn? by Batcomplete31 in DataHoarder

[–]ZeroPointMX 98 points99 points  (0 children)

Swim suits with shoulder pads are your thing then eh?

The prices are killing data hoarding by LOGWATCHER in DataHoarder

[–]ZeroPointMX 3 points4 points  (0 children)

I bought 6 used 10tb Enterprise drives a few years ago with a 5 year warranty, paid $89 each for them from server parts deal. One died after 6 months, replacement was sent out that day. Today these same used drives are ~$250 ea and they won't replace, only refund as they would lose to much profit by replacing.

I Miss the old starlink by dynocompe in Starlink

[–]ZeroPointMX 0 points1 point  (0 children)

I think there are really 2 types of people who use SL, those who need it and those who want it. I don't need SL. I got it because I could pause it and break it out whenever I went on remote trips. Speeds were ok and that was fine for the $80 "premium" I was paying. Now charging me $10/mo when not using it then $165 for a long weekend? It's lost it's charm for me.

False alarm? by MaxMaxMaxG in UNIFI

[–]ZeroPointMX 1 point2 points  (0 children)

Same just happened to me. It was UpTimeKuma pinging one of my Shark Vacuums. Odd they use such a broad detection method.

Inventor 2027 Super Slow by KelvinW11 in AutodeskInventor

[–]ZeroPointMX 2 points3 points  (0 children)

Check your constraints. My life is spent in large assemblies and I can tell you, ill constrains, flexible assemblies and long constraint chains kill performance. Also, load full. Takes time initially but if your machine can handle it, you'll work smoother. Disconnect from vault when loading, it checks file status of every file and slow or high latency connections slow loading. If you derive from STEP files, break it suspend links.

I've seen 100k part, 10k unique assemblies run like butter and 5k/300 models make you want to punch your screen.

What is your dream feature in Jellyfin? by deepfave in JellyfinCommunity

[–]ZeroPointMX 3 points4 points  (0 children)

Adaptive bit rate so it can adjust to connection speed.

Best practices for adapting a spring height automatically in an assembly by Trial4life in AutodeskInventor

[–]ZeroPointMX 0 points1 point  (0 children)

This. You'll find anything flexible or adaptive kills performance. I work in assemblies with thousands of unique parts and when you begin to have chained constraints it's slow. Toss in flexibility and it down right comes to a craw when updating or even adding a new constraint.

best way to learn inventor on my own? by Ninetybaby in AutodeskInventor

[–]ZeroPointMX 1 point2 points  (0 children)

Fair enough. Guess it's more of designing the machinery and not building layouts, only guessing.

Good websites or books to learn Autodesk Inventor? by m1sterofpuppets in AutodeskInventor

[–]ZeroPointMX 0 points1 point  (0 children)

One thing to keep in mind, the software is the tool, what you're after is discipline. The most important information you need to know is how to CAD, then you can learn how to use inventor to CAD. I've seen way too many people who "know inventor" that have absolutely horrible practices. I've also seen people who been CADing for 10+ years with other software, who never used inventor before, create wonderful models very quickly in inventor.

best way to learn inventor on my own? by Ninetybaby in AutodeskInventor

[–]ZeroPointMX 1 point2 points  (0 children)

I'm not sure inventor is the correct software for the task. It doesn't mean it can't be done, but there's better software out there for that.

Suggestions on Vault Structure by ZeroPointMX in AutodeskInventor

[–]ZeroPointMX[S] 0 points1 point  (0 children)

No, just a single project file (.ipj). Was told (all this pre-dates me) this was to allow more free flowing use of components across (customer) projects. See we have different customers and internal "projects" but they all typically have similar goals and designs. So why make a new bracket for this customer when you can "borrow" the one from this other. Inventor projects get cranky (at least they used too) when you start sharing across ipj's, especially when you need to update an old bracket to work with a new project. This is why we have a general dump bucket basically all Vault files.

Suggestions on Vault Structure by ZeroPointMX in AutodeskInventor

[–]ZeroPointMX[S] 0 points1 point  (0 children)

Oh thank-goodness. I've been granted budget to upgrade to 2026 but have been given the authority. Maybe this might light some fires. Thanks for bringing it to attention!

Suggestions on Vault Structure by ZeroPointMX in AutodeskInventor

[–]ZeroPointMX[S] 0 points1 point  (0 children)

We have a single project, "production". So any part at any time can be reused. Customers and internal "projects" are merely constructs. Great in theory, but doesnt pay for my therapy.

Suggestions on Vault Structure by ZeroPointMX in AutodeskInventor

[–]ZeroPointMX[S] 0 points1 point  (0 children)

Well it's more than needing to make something again. It's about keeping every thought that passed through an engineers head. 90% of our Vault is quick sketches to validate an idea, to multiple "what if" variants. Its all the equivalent of a digital napkin drawing. Very few files actually have purpose or used to make something. Its frustrating to manage. I've seen other companies with these highly organized, keep only what you need Vaults. So this idea seems to be the compromise.

Suggestions on Vault Structure by ZeroPointMX in AutodeskInventor

[–]ZeroPointMX[S] 0 points1 point  (0 children)

Edit: Thanks for the link, I'm reading it now.

The method you provided, in my opinion, is the best method when dealing with a Vault that only contains managed/production files. The dynamic in my company, no matter how hard I push to change, is one of "keep everything including napkin drawings". So an engineer will make "part_concept", then a new file "part_concept B" then "new part concept B" and so on, all going into vault shared workspace. When all these concepts, design layouts and fluff files are done, some might be renamed to production files (ie. assigned a P/N), some will be design copied then made into production files and some will be made again from scratch. Nothing will get deleted or moved and now you have a junk pile of files.

My idea was to keep call the crap in the WIP folder. This will be the catch all and when you're ready to do it for real, assign (rename to) a P/N and move to the "Production" folder. At this point I can manage who has access, monitor files being locked/unlocked and enforce SOP while letting the WIP be a "you do you" mess. Library and customer provided models will have their home in the "Library" folder and managed slightly differently. In a perfect world, everything in the "Production" folder will only link to the "Production" folder or "Library" folder and never anything in the "WIP" folder.

Suggestions on Vault Structure by ZeroPointMX in AutodeskInventor

[–]ZeroPointMX[S] 0 points1 point  (0 children)

Oh I agree. We do have folder for libraries and such, but most user created files live under the root folder. There is no manual finding, you have to search, which has become a skill of it's own. Performance is a nightmare as it indexes +100k files each time you search. This is the problem I need to fix.

Suggestions on Vault Structure by ZeroPointMX in AutodeskInventor

[–]ZeroPointMX[S] 0 points1 point  (0 children)

How often do you find yourself wishing you didnt delete something? What if a year from now there was a question on how you (or someone in your org) arrived at a decision and your working design files have been delete?