[QUOTE=Dylan14;526770]I did try that, but it didn't work as it gave me the same error.[/QUOTE]

I hope this doesn't come across as strange. But "make friends" with your environment.

You stupid human; it deterministic machine doing *exactly* what you tell it to do.

You're actually smarter than it is. But it will try to disprove this axiom until you assert your authority, and it begins to do what you tell it to do.

FWTW...

[QUOTE=Corbeau;522755]...Users get free access to a Tesla K80, which is much, MUCH quicker than my poor CPU...[/QUOTE]

This would be good for those who do not have access to a higher power GPU. My older HP system could use this. I wonder what the sharing bottleneck would be?

[QUOTE=storm5510;526776]This would be good for those who do not have access to a higher power GPU. My older HP system could use this. I wonder what the sharing bottleneck would be?[/QUOTE]

Really? Cool.

Hadn't thought of that...

[U]Off-Topic[/U]:

[QUOTE=chalsall;526775]...But "make friends" with your environment.

You stupid human; it's a deterministic machine doing *exactly* what you tell it to do.
[/QUOTE]

@OP: If [B]chatsall[/B] means what I think he does, then the old adage about the carrot and the stick applies. You [U]never[/U] want to use the stick with this group. You'll be eaten alive. There also is a cascade affect. Get on the bad side of one member and others will follow. Be mindful of what you write. If you ask a question, make it clear and precise. Above all things, be respectful!

I've been a member here since 2009. I had to learn all these things, and it did not happen overnight. I now believe I have the respect of a few members here. When you gain that, they will pay far more attention to what you write or ask.

[QUOTE=storm5510;526805]@OP: If [B]chatsall[/B] means what I think he does, then the old adage about the carrot and the stick applies[/QUOTE]The machine does what it does as it is told. If a system has peculiarities, it is up to the programmer to understand that and deal with it. If you think it should be $verb #noun, but the system wants $noun #verb, so be it. Do it the way the system wants.

In a prior post it looked like you were wishing for something that has already been delivered. Namely, those that don't have GPU's getting free access.

[QUOTE=Uncwilly;526828]The machine does what it does as it is told. If a system has peculiarities, it is up to the programmer to understand that and deal with it. If you think it should be $verb #noun, but the system wants $noun #verb, so be it. Do it the way the system wants.

In a prior post it looked like you were wishing for something that has already been delivered. Namely, those that don't have GPU's getting free access.[/QUOTE]


Point taken. I'll just go stand in the corner now. :smile:

[QUOTE=storm5510;526805]@OP: If [B]chatsall[/B] means what I think he does, then the old adage about the carrot and the stick applies.[/QUOTE]

My apologies if my somewhat flippant post was taken the wrong way.

What I was /trying/ to say is that there are a tonne of opportunities to use this newly discovered resource for all kinds of things. TF'ing might be a sub-optimal usage case for the K80s, T4s and P100s we have suddenly found ourselves with.

I implemented a "proof-of-concept" solution, focusing on TF'ing, because I just happened to already have a server configured to coordinate such efforts. Relatively trivial for me to graft on the needed back-end functionality to make this work.

I strongly encourage others to expand on this, to focus on other things. P-1'ing, LL'ing, et al. As a sole HPU ("Human Processing Unit"), I only have so many cycles.

Lastly, I consider computer programmers to be inherently stupid. Or, at the very least, error-prone. And the kit will (usually) do ***exactly*** what we tell it to do. The coveted instruction "DWIM" ("Do What I Mean") reflects this. As does my common explanation for why something isn't working correctly because of a mistake I've made: "SPE" ("Stupid Programmer Error").

Programming isn't easy. It's a lot of fun, but not easy... :smile:

I kept on receiving this error when trying to run GPUOWL on kaggle. I suspect that it's a gcc version issue but i can't find gcc8 in the package list no matter if I add ubuntu-toolchain-r/test repository or not. What should I do
[CODE]./gpuowl: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.11' not found (required by ./gpuowl)[/CODE]

[QUOTE=xx005fs;526913]What should I do[/QUOTE]

Quick suggestion: try building the executable within a Kaggle instance.

Dylan has given above examples of building packages from source, by way of the Python shell. IMO, a useful skill-set in and of itself.

And, while you do this, think back to those old grey-haired guys, who used to submit "batch-jobs" to the "one-eyed gods" for execution way-back-when. Often by way of holes punched into paper products; sometimes taking days for the results to come back...

(Sorry; some will find the humor in that more than others...)

[QUOTE=chalsall;526914]Quick suggestion: try building the executable within a Kaggle instance.

Dylan has given above examples of building packages from source, by way of the Python shell. IMO, a useful skill-set in and of itself.

And, while you do this, think back to those old grey-haired guys, who used to submit "batch-jobs" to the "one-eyed gods" for execution way-back-when. Often by way of holes punched into paper products; sometimes taking days for the results to come back...

(Sorry; some will find the humor in that more than others...)[/QUOTE]

I'll try to build using Dylan's ways i guess as I tried using the makefile but it can't ever find the libraries it need despite that gmp and all the other required stuff are installed.
(On Colab GPUOWL builds without a problem and works right away, but on Kaggle even though the search path for GCC is in /usr/linux-gnu/ which is where libgmp is installed, but it still can't find it for some reason)

[QUOTE=xx005fs;526919](On Colab GPUOWL builds without a problem and works right away, but on Kaggle even though the search path for GCC is in /usr/linux-gnu/ which is where libgmp is installed, but it still can't find it for some reason)[/QUOTE]

OK. I'm afraid I have no cycles to help you figure out what's going wrong here.

But... The Notebooks' Sections are just blocks of Python. Consider it a shell, which is batch run. Add as many sections as you like; they all run in the same Virtual Machine.

Single command at a time is allowed. Just type it in (with a preceding "!"), and click "Run". Observe results. Rinse and repeat...

Use the available Linux command-line functions to figure out what you're missing, and how to fix it. For example:
[CODE]!find / -name "*gpu*"[/CODE]

Heck, even strace is available, if you want to get deep and serious! :chalsall: