Jump to content

Koppa315

Member
  • Posts

    44
  • Joined

  • Last visited

Everything posted by Koppa315

  1. I think it gets disabled and hidden after a certain point into the show. I made one order and then was contemplating a second because I missed adding a message to the first (wasn't thinking and too excited about the sweatpants) and wanted to comment on the Ti things but didn't see a box for merch messages. If this is true this it is a confusing user experience, I'd believe it would better to be visibly disabled & indicate that you're not accepting more at that point. My guess is your merch team is getting a lot of notes that are merch messages for the show and not messages to the merch team about their order... unless I'm confused on the order page design. (edit: to nest correctly as a reply)
  2. Credit goes to @danielocdh for creating this, I've only been making some updates and created a GitHub gist so we can track it a bit easier Nice setup for folding @Harpo!! I'm currently on two GTX 980s and every month I try to spin up an Azure VM since I have credit on there from work for free (might as well use it for something right?)
  3. Always good to question random scripts from the internet. The script uses the F@H Client Telnet Protocol described here By default F@H allows connections from localhost on port 36330 with no password, so if you just leave the script as is it will try to connect to localhost:36330 with no password. There are commands that could be used to set User/Team/Passkey as part of the options commands but if you scan through they are not being used. I believe they are: option user <username> option team <team number> option passkey <passkey value> Where technically you can set multiple at a time. There is one call that I added to the last iteration of the script to check for new versions of the script by calling to the GitHub gist location which you may disable if you do not feel comfortable with the script reaching out to the internet. I'm also thinking of updating it to take a config file instead of the values built into the script so that between upgrades it does not cause you to have to transpose the values that you've changed from default each time...
  4. Are you choosing COVID-19 only? If so it might be that there are insufficient WUs at times.
  5. My one buddy had to remove all slots, then re-add the GPU and then it took it, after that he added his CPU and things were happy again.
  6. 1 & 2) I generally run Ubuntu systems as they're easy for care and feeding. If your comfortable with command line Ubuntu Server isn't bad, if you want a GUI I'd go with Ubuntu Desktop. I normally stick to debian based distros otherwise when I toy around with em. As @Inkertus said, it's all depending on how comfortable you are with command line or I would add how technical/comfortable with learning you are. 3) From Windows to Linux, depends on if you have a GUI and/or if your comfortable with command line. If you're running something like Ubuntu Desktop you could install a VNC server and use that to kinda be like remote desktop or the messy route of xWindows Forwarding but TBH it's easiest to use SSH and learn command line for it. Also if it's for managing F@H then use the advanced controls on your windows machine to control it. If you just want stats and basic management of the Ubuntu system look into cockpit it's easy to use: Cockpit 4) Babysitter does work on Linux just make sure you have python3 installed Note: Folding@Home uses Python2 which is no longer really supported, so depending on the version of linux you install it may no longer be automatically installed (Python3 might) so you may have to install Python2. Current LTS of Ubuntu 20.04 you must install it via package manager
  7. Good point @CWP, I don't disagree that many distros would normally ask you to give execute rights to the script, I think the part that is working for us here is that the script is normally not being downloaded but copy and pasted into a file vs if the file was directly downloaded in which case a modification of execution rights would definitely be needed.
  8. Ah likely you're potentially still running using Python 2, can you please try running python3 FAHbabysitter.py
  9. Ugh as someone who has to admin Windows servers every day it drives me insane... IIS with .NET applications (2.0 - 4.5) is asking for headaches at times. 4.7.x isn't as bad, but can still be annoying and .NET Core is generally OK after .NET Core 2 To be honest containers has made admin a lot less of a headache, don't have to worry as much about babysitting the OS
  10. Should, if you have python3 installed Sorry I say should as I don't remember the last time I ran a Linux system with a head lol
  11. If you need any other video cards to betray you hit me up, haha
  12. Should look something like: Double clicking on the script should work as well for most people.
  13. Unfortunately this has been happening to a few people: WS have been busy from some reports, other times people are saying that restarting FAH has fixed it, mostly it's waiting for the WU to be accepted. There have been some reports that the WU has timed out and the WS won't accept it and that the credit is lost, but that was only one report I saw in the GitHub issue tracker. In that same issue there was mention that some are looking at working on an update for Work Servers to tell Clients why an update wasn't accepted better as the client has no idea what's going on when a WU isn't accepted.
  14. Creating a place to discuss the Folding@Home Babysitter script It has been noticed that pause and un-pausing slots that are stuck in a waiting status looking for work has improved the clients ability to connect and download work units. That's where the Babysitter script that @danielocdh wrote comes in, it checks the Folding@Home client periodically and pauses and un-pauses slots that are stuck waiting on Work Server Assignment. A few people are using this now to try to help manage Folding@Home clients, so I figured it might be easier to create a topic on it for instructions, feedback, in case people are having issues and to provide updates. Easier than running around the different topics that have referenced it. I've been working with @danielocdh to update this script here and there to ensure it works with the recently released version of the Folding@Home Client and fix other issues and add new features It can be found on GitHub currently, as of writing this topic, the script is at version 1.8 and will now tell you periodically if there are updates. At the top of the script you can find options as well as a how to for installing Python 3 Installing Python 3 on Windows: Installing Babysitter Script on Windows: Options Available:
  15. So if you move a protein from one version to another it learns how to fold it into a square Good catch though, I was wondering what happened to that beast.
  16. Ummm the virus is shy and would like it's privacy thank you
  17. I love your naming convention, at my place we use a random name generator, e.g. one server is whalegrade, funny enough it's a little 1U atom server... such a big name. The NAS is Serapeum (short for Serapeum of Alexandria) though that was self named. Then there are a bunch of others on the ProxMox server. Glad it's working for you @RollinLower, was there something weird going on or something we should try to fix for in the future? Also thanks @marknd59 for helping people get started! I've included a paraphrased version of your instructions as update 1.7 in the gist, probably should have had instructions
  18. Whooops, so sorry, I quoted you and missed entering my response for your quote, the card thing was to @bafo_ah who has been playing around with all the api stuff. For you unfortunately there has been reports on GitHub of WUs getting stuck and for the most part they are saying that you just have to wait it out. Some times exiting and re-opening has triggered it to upload for some people but it was random. It seems that work servers are getting overwhelmed, other times it's because the WU has timed out and they no longer are accepting it, if this is the case the WU will eventually disappear on it's own and won't count for credit . There is an enhancement that is being requested on the issue tracker for the work server (WS) to send more details back to the clients to inform them of what's going on with the WU that is being sent in specifically for the later case where the WU is no longer going to be accepted.
  19. Interesting, even with MSDN credits? Must think the brits are sneaky Or it could just be that my MSDN is associate to an enterprise account so if I do something stupid they can likely have me fired I don't disagree on the more confusing, though after bashing my head in for a while I just winged it by creating a VM and it setup the storage, pools and everything else for me and then provided me with a template if I wanted to deploy it in the future.
  20. I saw on the GitHub issue tracker for FAHClient a few people were having that issue, have you posted you card and the version to the tracker? I think they've cleared up a few cards so far. Awesome to hear that it's working @marknd59! Meh, experimenting is how you learn right? Trust me I had to do a lot of that for updating @danielocdh's code, I haven't touched python in 9+ years Awesome thank you @danielocdh, I'll go review! No worries, glad the updates were useful I've heard that a bunch with Google, you almost need to preemptively stop much earlier since it's constantly caching up on the billing page. Granted you did an amazing job only getting £0.44 over. I haven't played with my Google credits yet, was contemplating setting up a Terraform instance just to learn the tool and play with some credits across my Google accounts and MSDN Azure Account. For Azure MSDN Credit you get to use all of your credit without adding billing information, including GPU systems, but if you use all your credit before the month is up the instances disappear. So if you kill it with enough credit for the storage costs to continue for the remainder of the month you're good and can start all over again the next month, just in case having a Terraform job ready to spin back up a node the next month might be nice so I don't have to babysit the cost analyser (or script it... hahaha).
  21. Trying to keep the rainbow puke in check, normally it's just running some lowest brightness single colours, but can make it full on rainbow puke since there are a few Corsair products in there I was originally using the motherboard fan headers and ASUS does have control software, unfortunately I'll be adding more fans soon so the commander having the ability to control 6 fans with curves is nice, I could also use y-splitters but depending on the device some of them do weird things in reporting. From what I heard the standard is to send fan 1's RPMs but some send each in sequence which can get very confusing to any control software I've tried uninstalling and reinstalling, I haven't tried downgrading yet. I've also tried force upgrading the firmware on the Commander Pro, which stabilized the fans even showing on the PWM control and for some reason they were always there for RGB control (Corsair has their priorities in pretty colour land?) Funny enough it seems like killing the iCue services causes the fans to ramp down. Granted the loudest fans for now are the videocard fans, I'm wondering if I should disassemble, clean and see if thermal paste is dead on them. Also a bit more airflow would help them.
  22. Still can't get my system to be quiet, thinking my Commander Pro is busted It was an open box that they weren't supposed to sell me as I purchased full price, but because of COVID-19 they couldn't take a return and I have to wait till end of the pandemic... Need to talk to them again as their parent company has changed their return policy since. I can't seem to set a RPM target for the fans at all, they always run at basically 100% lol Granted after scavenging another GTX 980 SC ACX 2.0 to toss in my system I'm running into the bottom videocard being 10c cooler than my top one
  23. The PyON API Version not the FAHClient version, they played around with some spacing and such that broke the codebase for the babysitter script because it uses telnetlib with expect regex which left it susceptible to minor changes causing some headaches. Some of it may be alleviated by performing evals like you have in your codebase, but evals always make me uneasy especially when coming from an API/remote party, maybe with disabled global scopes and disabled local scopes? (I don't think the message will require either?) I've been reading through your code it's cool, I haven't run it yet, just scanning through what it does. Seems like yours is pretty far ahead in what it handles
×