another ++;

Our RAC falls like a rock without the replica and when it reaches zero, we all can't post here anymore...

I'd think that would take quite some time to occur, like months if I understand the calculus.
For whatever reason even with the replica down something still goes on, as I'm seeing increases in my RAC today.

---

another ++;

Our RAC falls like a rock without the replica and when it reaches zero, we all can't post here anymore...

I'd think that would take quite some time to occur, like months if I understand the calculus.
For whatever reason even with the replica down something still goes on, as I'm seeing increases in my RAC today.

Considering credit generation has nothing to do with the replica server it would indeed take a very long time.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

I think now the regular dB is being used to do the replica r/o accesses, as I can see WU's dated 1/25 and later AND my validation waiting count has finally changed. Even though the replica is still offline.

Yay!

---

another ++;

I had to look at that twice to realize that's not a snippet of code. :p

I've come up with some weird variable names in some of my code before. I had instructors in high school and college that groaned and face-palmed at some of my work. I have a habit of doing stuff like 'temp' 'temp2' 'temp3' 'temp4' 'blah' 'blarg' 'something' 'nothing' 'somevalue1/2/3/4' .....and I'm terrible about not using comments all over the place to explain what's being attempted with every section or line, so.. I started doing comments that were basically "/* Here is a comment because apparently I'm supposed to have comments everywhere even though *I* know what's going on and the code works, so if it works why do I need to annotate every single thing I do? */" Yeah.. they didn't really like those comments, either.

Aside from the fact that all my programs worked flawlessly (and were even built to be crash-proof (like being able to detect and reject an ASCII character when it was expecting 0-9, even though the assignment said nothing of the sort), the biggest complaint/gripe my instructors always had: I'd whip up my comment-less code in 15 minutes.. in class, instead of as homework, THEN draw all the flowcharts after the code was done. Apparently you're supposed to do the flowcharts first. Yeah. My brain doesn't work like that.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Well - comments are made to help others understand your code so they can correct and/or expand it to new functionality long after you've left the building. That's why your instructors are teaching it, to make it a habit for those who go out and code professionally.

The errorfree (professional) program still has to be written.

Well - comments are made to help others understand your code so they can correct and/or expand it to new functionality long after you've left the building.

I also find them useful to understand

myOwnCode()

when I have to go back to it long after it has left my head.

---

Take it from a long-time professional programmer, code without comments (or with only trivial comments) is useless when maintaining systems written by long-gone coders.

Programming in the real world is NOT like in the movies or on TV - it is having continual revisions in everything with time - kinda like evolution. So useful comments (and useful variable and storage names) can make all the difference in the world.

---

I know comments are important in a professional/collaborative kind of situation. I'm reasonable about actually doing useful comments if it's something that I'm going to share, but all the assignments for the classes were basically just glorified calculators, or doing a bubble sort of 10 random inventory items read from a text file.

I just didn't see the need to explain "And here we add 2+2 so that we can find out in about 10 lines that it does in fact equal 4" like the instructor wanted me to do. I would explain what a whole function was supposed to do, but wouldn't annotate every single line of the code.

If I'm working with others though.. yeah, annotations are necessary, but not if it's just me being bored and fiddling around with seeing if I can automate mundane tasks. *shrug*



edit: re: "comments are made to help others understand your code so they can correct and/or expand it to new functionality long after you've left the building."

As a studious reader of BOFH... I know it's not very nice and all, but... if I've left the building... why should it be my problem if nobody can understand my code? It's not like I'm still there to deal with it. *shrug* :p If anything, I should have taken my code with me when I left, mostly because.. my code aren't quite "programs" as much as they are just calculators and glorified shell scripts to streamline things a little better, because.. well, I'm lazy, so if it saves me from SSH-ing into 15 boxes and running the same few commands on each one.. I'm making a script to do it for me.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

I think now the regular dB is being used to do the replica r/o accesses, as I can see WU's dated 1/25 and later AND my validation waiting count has finally changed. Even though the replica is still offline.

Yay!

Still not right though as I show nothing dated later than yesterday at 17:00 UTC, which was pre-outage.

My main machine gets through a GPU WU in around 20 mins.

Just watched 2 tasks complete and upload, still no change.

---

Maybe it was a temp thing, then, or just a plain mistake. I am seeing no change from about 6 hours ago, at the moment.

EDIT: Correction: Checking tasks shows latest tasks sent 1/26 17:00UTC, about 18 hours ago!

---

Ahh...the kitties spy the replica DB is back online....although currently some 70,772 seconds behind real time.
If it does not crash again, hopefully it comes back up to speed quickly.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Just noticed on SSP, replica is back, a mere 70K seconds behind. Go, baby!

---

Now the Replica database is back online does that mean we might get some results exported !

---

.


A person who makes no mistakes, creates nothing.

Now the Replica database is back online does that mean we might get some results exported !

The stats dump is a separate process. Which they often disable when there are db issues. It may get enabled once the replica catches up. Provided someone remembers to go in and enable it.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

The replica is now only 10 1/2 hrs behind, it's catching up.

---

The replica is now only 10 1/2 hrs behind, it's catching up.

At its current rate it should be caught up in about 4 hours.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

The replica is now only 10 1/2 hrs behind, it's catching up.

At its current rate it should be caught up in about 4 hours.

It looks like it has caught up.

---

The replica is now only 10 1/2 hrs behind, it's catching up.

At its current rate it should be caught up in about 4 hours.

It looks like it has caught up.

Eyyyy! :D, time to bring up the Mac and Linux machines, and get some packages ready for Eric.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Hmmmm....
Just wondering if we are out of the latest batch of 2015 Aerecibo data already.
I noticed the last batch loaded into the splitters was more of the 2011 stuff.
Not that it's really any problem, and redoing old data might be even more justifiable now that it is being done with the newer more sensitive v8 applications.

Just wonder if we have really done all of the newest stuff already...if so, that didn't take long.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

The replica is now only 10 1/2 hrs behind, it's catching up.

At its current rate it should be caught up in about 4 hours.

It looks like it has caught up.

Eyyyy! :D, time to bring up the Mac and Linux machines, and get some packages ready for Eric.

:)