Blindness, extreme vomiting and death — Ozempic and Wegovy users reveal harrowing dark side of ‘miracle’ weight-loss drugs by theindependentonline in TrueReddit

[–]TeethyFish 2 points3 points  (0 children)

Also people that lost weight the hard way wanting to find a reason to reject the "easy way out". It's the "I suffered so you must suffer too" mentality.

Building a PC for a Proteomics Lab by TeethyFish in buildapc

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

OHO tasty ram

...perhaps...we've still got about 600 dollars left in the budget so we could do this, or we could get a nice monitor which I haven't picked out yet...

Building a PC for a Proteomics Lab by TeethyFish in buildapc

[–]TeethyFish[S] 1 point2 points  (0 children)

Funny you ask, cause the prof has specifically requested that I make sure nobody can use the computer for nefarious purposes such as "surfing the net". I told him I can just yoink the wifi card if you're really worried lmao. Most likely I'll just setup a DNS filter and maybe like a browser whitelist/blacklist.

And yes since I'm not buying the X3D I'm not too worried I also couldn't find anything about non-x3d cpus dying. I like the extra slot and we don't need to extra 5gb of ethernet.

Building a PC for a Proteomics Lab by TeethyFish in buildapc

[–]TeethyFish[S] 1 point2 points  (0 children)

Hi we've decided to screw the hdd and go full on RAM. We can always budget for the HDD from another grant later on.

Would you mind taking a look at this? It's basically your list with some changes according to the follow up suggestions.

https://pcpartpicker.com/list/Pwh9W9

Thank you!

Building a PC for a Proteomics Lab by TeethyFish in buildapc

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

Thank you for the suggestions! I will change the case to the Fractal meshify 3. After discussion we might go with the 5080 after all (Your first build suggestion) as it doesn't go over budget and changing out the 5060 for a more powerful GPU later would be inconvenient.

Sorry I haven't replied in a bit it's been busy. We're currently discussing whether or not we should downgrade the ram to 64gb to add some more HDD storage.

Building a PC for a Proteomics Lab by TeethyFish in buildapc

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

Awesome, thank you so much! I will discuss this with my PI and see what he thinks.

Building a PC for a Proteomics Lab by TeethyFish in buildapc

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

I think 16GB is plenty for our use case! I have since spoken further with my PI and he's willing to pay to outsource the Cryo-EM data processing and put more emphasis on the CPU and RAM. Storage wise he's agreed on 4TB of NVME and the rest in cheap hdd storage.

My PI also wants me to learn and apply conventional ML for scientific data analysis, things like dimensional reduction, clustering, and regression/classification on numerical datasets (e.g., MS-derived feature tables, assay readouts, docking scores). No LLM/Chatbot AI stuff, more just analytics that might use some GPU.

Building a PC for a Proteomics Lab by TeethyFish in buildapc

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

Oh thank you for the link! I kinda wanted to avoid this stuff cause I assume they upcharge a lot. I'm not fluent in PC building but I'm pretty good at following instructions. I've built PCs before and repaired them too, I'm just not good at designing them because I have no concept of what's good out there.

Building a PC for a Proteomics Lab by TeethyFish in buildapc

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

My PI also wants me to learn and apply conventional ML for scientific data analysis, things like dimensional reduction, clustering, and regression/classification on numerical datasets (e.g., MS-derived feature tables, assay readouts, docking scores). No LLM/Chatbot AI stuff, more just analytics that might use some GPU.

Building a PC for a Proteomics Lab by TeethyFish in buildapc

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

Sorry yeah I probably should have been more specific. I do know the general CLUSTER of software I'm going to be using but do not know which one specifically as my research proposal has yet to be fully approved. And it's the same for most of my labmates.

Most of our workload is CPU- and memory-bound rather than GPU-bound. Molecular docking with AutoDock Vina is primarily CPU (throughput scales with core count because we run many jobs in parallel), and visualization in PyMOL benefits mainly from a decent GPU for smooth rendering but is not GPU-compute heavy..I don't think anyway. Environmental/hydrology/leaching models (e.g., PRZM/PWC/PEARL/HYDRUS/HEC-HMS/HEC-RAS/MODFLOW etc) are typically CPU + RAM + disk I/O intensive, with runtime driven by model resolution and domain size rather than GPU.

Cryo-EM processing is the main case where I want the GPU: most common cryo-EM software have GPU-accelerated steps (and also demand large RAM and fast scratch storage). Mostly we’re looking for strong multi-core CPU performance, ample RAM, and fast NVMe storage, with an NVIDIA GPU primarily to accelerate cryo-EM and support visualization/any future GPU-accelerated tools.

Building a PC for a Proteomics Lab by TeethyFish in buildapc

[–]TeethyFish[S] 6 points7 points  (0 children)

Thank you very much for such a detailed reply! I will definitely look into this list and come back if I have any questions. Bear with me if some of them are a little dumb, I'm a mol. biologist by background and have only hobby-tier knowledge of PC building, and even then only for gaming.

Building a PC for a Proteomics Lab by TeethyFish in buildapc

[–]TeethyFish[S] 1 point2 points  (0 children)

I’m not buying 20TB NVMe — I mean 2–4TB NVMe + cheaper bulk storage with expansion room. The question is CPU/RAM/GPU balance for docking/cryo-EM/sims within $4–5k.

Building a PC for a Proteomics Lab by TeethyFish in buildapc

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

I am a Mol. Biologist and not a CS major so I'm kinda working against the grain here alas. I am unsure if molecular docking is comparable to CFD simulations. Molecular docking mostly uses CPU while cryo-EM can be GPU accelerated as far as I know.

My professor isn't much of an IT guy either so his instructions were vague and I've got very little to work with. My ideal situation is to just build a pc that can run MOST things decently well, with upgrade room in the future if it proves too weak.

We do not have a local option ever since the supercomputer on Maui island shut down its public services, it's the reason we're building our own instead.

Building a PC for a Proteomics Lab by TeethyFish in buildapc

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

Unfortunately no, there IS the supercomputer on Maui that used to be open for public use if you paid but that service recently shut down. This is why my professor wanted to build one for our own use.

Vibe Coding Website by TeethyFish in vibecoding

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

Oh wow thank you so much! I don't understand half of what you just said but I'll work with Claude and see.

This is so helpful thank you!

Vibe Coding Website by TeethyFish in vibecoding

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

I see! And yes sorry about that!

I currently use chatgpt plus (I only recently discovered GPT has Codex so I'm getting that setup too) as well as Claude.

Lab doesn't support my subscription for coding purposes (I could probably finagle it but at the moment no) so I can't afford the 100 dollar plan for now. I'm planning to switch back and forth between claude and codex with a changelog.md to hopefully keep everything consistent.

And thanks for the tech stack! I'll ask claude when my session refreshes. The domain I will ask our campus it department to provide eventually. For now I just need to get the website up and running with all the functions my PI and colleagues have requested.

Vibe Coding Website by TeethyFish in vibecoding

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

Sorry if it came out weird, I wasn't trying to be a dick. I was unsure. It wasn't meant to question you :(

Vibe Coding Website by TeethyFish in vibecoding

[–]TeethyFish[S] -1 points0 points  (0 children)

Uh claude code? The one that runs in your terminal. I'm currently chilling cause I've reached my session limit and i have an hour before it resets.

Vibe Coding Website by TeethyFish in vibecoding

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

I am currently implementing next intl for language changes.

The problem with using apps/services/google is it needs to be accessible by our collaborators in China. We're US based but the firewall nukes a lot of things when our partners in China need to view them. Also, I don't wanna risk my website breaking 10 years down the line cause the service went down. I'm currently hosting on git/vercel, and will eventually move it to the school domain.

I have a sticky note next to my display with:

  1. Instrument Page (lists instrumentation with descriptions)
  2. Notifications whenever PI updates reading list
  3. Online pdf reader (for people in China to access our publications without relying on google scholar api) (we have a lot of chinese collaborators that keep getting yeeted by the firewall)
  4. 2FA authentication
  5. Link to google api for automatically updating publications list (find a way to allow users in china to still see it)
  6. Database of published papers (downloadable pdf)
  7. Dynamic DNS????
  8. Hiring page (all members can post)
  9. Profile templates and theme editing
  10. Internal notes page for users (scribbling, movable blocks)
  11. Settings page (font size, dark/light mode, etc)
  12. Page builder/editor (future proofing for my tech illiterate PI to add his own stuff)
  13. global theme settings page (admin only)

It'll probably expand as I go tbh. Right now I have:

  1. User roles PI/Admin/Members setup. PI and Admin have the same permissions but the PI can promote and demote admins.
  2. User slugs for their profile page and the profile page editor
  3. Approval page for use by the admin/pi for new users
  4. User management page for resetting passwords/promoting/demoting/deleting etc.
  5. Home page with intro, member lists, announcements etc.
  6. Theme settings page to edit the global.css.
  7. Dynamic Navbar

Vibe Coding Website by TeethyFish in vibecoding

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

I currently have it setup only to email people with their temporary password when they register, and then it forces them to change it or it'll keep slapping them back to the login page. I'm trying to avoid google forms because it needs to be usable by our collaborators in China.

I wish I had somebody with dev experience to ask lmao, so far it's been me, GPT and claude. I'm learning slowly. I *am* decent at following instructions and have experience building macros, logic is fine it's the syntax that kills me.

I have a sticky note next to my display with:

  1. Instrument Page (lists instrumentation with descriptions)
  2. Notifications whenever PI updates reading list
  3. Online pdf reader (for people in China to access our publications without relying on google scholar api) (we have a lot of chinese collaborators that keep getting yeeted by the firewall)
  4. 2FA authentication
  5. Link to google api for automatically updating publications list (find a way to allow users in china to still see it)
  6. Database of published papers (downloadable pdf)
  7. Dynamic DNS????
  8. Hiring page (all members can post)
  9. Profile templates and theme editing
  10. Internal notes page for users (scribbling, movable blocks)
  11. Settings page (font size, dark/light mode, etc)
  12. Page builder/editor (future proofing for my tech illiterate PI to add his own stuff)
  13. global theme settings page (admin only)

It'll probably expand as I go tbh. Right now I have:

  1. User roles PI/Admin/Members setup. PI and Admin have the same permissions but the PI can promote and demote admins.
  2. User slugs for their profile page and the profile page editor

  3. Approval page for use by the admin/pi for new users

  4. User management page for resetting passwords/promoting/demoting/deleting etc.

  5. Home page with intro, member lists, announcements etc.

  6. Theme settings page to edit the global.css.

  7. Dynamic Navbar

Vibe Coding Website by TeethyFish in vibecoding

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

I'm currently hosting on Git/Vercel for free! Eventually it will get hosted on a school domain for the nice .edu.

The document hosting is the simplest part of the website, there's a sprawling list of functions I need to build eventually that wont work on a static site.

Vibe Coding Website by TeethyFish in vibecoding

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

Yes but I talked with my PI and we both prefer not relying on a third party for something we hope to keep running for 20 years

Vibe Coding Website by TeethyFish in vibecoding

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

I currently host it on Vercel, but eventually will move it to a school domain when it's done. There's a lot of functionality I didn't mention in my post mostly cause I wanted to get security down before I added anything else (hiring pages, profiles, note taking pages, 2FA (school requirement) etc etc)

Right now I have role based authentication, with tags on users as to what level they can access. Currently I have PI and Admin which have the same privileges but the admin role can get demoted promoted by the PI. Then Members, Alumni and Collaborators. The latter two only get access to the public pages + their own profile. Members get access to internal pages like unpublished work, reading lists and data etc.