Announcement

Collapse
No announcement yet.

Oi Rattledagger...

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Oi Rattledagger...

    A low number of seti-wu.
    I will probably only produce 1 wu/week for seti the next 4 weeks.
    Even THINK gets a speed-up this way.

    Of course, if genome starts blowing up again, I will kill it off.

  • #2
    Oi Rattledagger...

    What do you feed your PC's to get results like that all of a sudden? I think another 3 days and we're 3 days neck & neck

    Jord.
    Jordâ„¢

    Comment


    • #3
      0.98 seems to blow up a lot less than 0.94 which blew up less than 0.93.
      [size=1]D3/\/7YCR4CK3R
      Ryzen: Asrock B450M Pro4, Ryzen 5 2600, 16GB G-Skill Ripjaws V Series DDR4 PC4-25600 RAM, 1TB Seagate SATA HD, 256GB myDigital PCIEx4 M.2 SSD, Samsung LI24T350FHNXZA 24" HDMI LED monitor, Klipsch Promedia 4.2 400, Win11
      Home: M1 Mac Mini 8GB 256GB
      Surgery: HP Stream 200-010 Mini Desktop,Intel Celeron 2957U Processor, 6 GB RAM, ADATA 128 GB SSD, Win 10 home ver 22H2
      Frontdesk: Beelink T4 8GB

      Comment


      • #4
        Well, I think I've seen a new problem.
        I don't know if it gave a error-message, but yesterday I got a client with this in the log-file:
        20010611 025943: SPA called
        20010611 025943: Initializing protein design algorithm
        20010611 030247: Designing protein sequence 12 of 30
        20010611 030458: SPA called
        20010611 030458: Initializing protein design algorithm
        20010611 030802: Designing protein sequence 12 of 30
        ... in endless loop. So I lost nearly 24 hours. Since it didn't actually crash, the THINK-client didn't get more done either.

        I killed the wu and got a new one, and we'll see if more things blows up.

        Comment


        • #5
          Keeps me at place 32 in the list for at least 24 hours longer

          Jord.
          Jordâ„¢

          Comment


          • #6
            Well, I speed up the THINK, since it hit 700 hours, and are currently working on the weekly seti@home-wu.
            Oh, yes, and flushed the results, so you're probably on place 33 by the next stats-update.

            Comment


            • #7
              Jordâ„¢

              Comment


              • #8
                Ah, temporarily back at place 31. At least in front of this mysterious k1l as well

                Jord.
                Jordâ„¢

                Comment


                • #9
                  Did you say I should give a couple of units to k1l?

                  Comment


                  • #10
                    Heck, NO !!

                    Let him/her crunch his/her own crunchies
                    And I've been d/ling new genes, with bigger unti-counts so I could beat him/her...
                    Jordâ„¢

                    Comment


                    • #11
                      Well, I've got two clients shitting themselves out, and one machine with crashed cpu-fan. Hopefully the cpu isn't damaged, but I'm currently killing off genome.

                      I'll wait for the next client, and in the meantime run seti and THINK.

                      So Jorden, the result I'll have on Sunday is your goal to overtake before the next client is out.

                      Comment

                      Working...
                      X