« on: June 13, 2020, 03:39 PM »
This topic has been moved to Post New Requests Here.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
HONK HONK, HEAR YE. I have created a goose for your desktop.
He'll nab your mouse, track mud on your screen... leave you a message, deliver you memes?
Play video games with a desktop buddy who will attack you if you poke him.
Fill out spreadsheets while your screen fills up with instances of Goose Notepad.
Unity Engine games developed with SpatialOS' cloud-based multiplayer Game Development Kit (GDK) are now in violation of Unity's terms of service, according to SpatialOS maker Improbable. The decision imperils the operation of many in-development game projects, including some that have already been released to the public.
Since its open beta release in 2017 (in partnership with Google), SpatialOS has allowed developers to easily integrate mass-scale multiplayer into their games by running a persistent version of the game in the cloud. But Improbable now says that a recent change in Unity's terms of service means the SpatialOS is essentially blocked from working with the Unity Engine.
The newly updated clause 2.4 of the Terms of Service now specifically excludes "managed service
running on cloud infrastructure" which "install or execute the Unity Runtime on the cloud or a remote server." Though the terms of service were changed on December 5, Improbable says Unity confirmed directly to them this week that the update "specifically disallow services like Improbable’s to function with their engine. This was previously freely possible in their terms, as with other major engines."
No matter how abundant or renewable, solar power has a thorn in its side. There is still no cheap and efficient long-term storage for the energy that it generates.
The solar industry has been snagged on this branch for a while, but in the past year alone, a series of four papers has ushered in an intriguing new solution.
Scientists in Sweden have developed a specialised fluid, called a solar thermal fuel, that can store energy from the sun for well over a decade.
"A solar thermal fuel is like a rechargeable battery, but instead of electricity, you put sunlight in and get heat out, triggered on demand," Jeffrey Grossman, an engineer works with these materials at MIT explained to NBC News.
The fluid is actually a molecule in liquid form that scientists from Chalmers University of Technology, Sweden have been working on improving for over a year.
This molecule is composed of carbon, hydrogen and nitrogen, and when it is hit by sunlight, it does something unusual: the bonds between its atoms are rearranged and it turns into an energised new version of itself, called an isomer.
Like prey caught in a trap, energy from the sun is thus captured between the isomer's strong chemical bonds, and it stays there even when the molecule cools down to room temperature.
When the energy is needed - say at nighttime, or during winter - the fluid is simply drawn through a catalyst that returns the molecule to its original form, releasing energy in the form of heat.
"The energy in this isomer can now be stored for up to 18 years," says one of the team, nanomaterials scientist Kasper Moth-Poulsen from Chalmers University.
"And when we come to extract the energy and use it, we get a warmth increase which is greater than we dared hope for."
A prototype of the energy system, placed on the roof of a university building, has put the new fluid to the test, and according to the researchers, the results have caught the attention of numerous investors.
|Version||Pre-Release (Test) - 20:14GMT - 04/11/18 (E66-193C)|
|Short Description||Learn languages through audio immersion|
|Supported OSes||Windows 10 (Only one I've tested on) - Probably 7 and 8 too. (.NET 4.6.1+)|
|Download Link (Portable)||Download (Google Drive): https://drive.google...PCuLBC5ps19e_f5lS5fH|
|Last Updated||08:36GMT - 1st November 2018|
|Example Word List (Italiano)||Learning.txt (38.76 kB - downloaded 349 times.) (Some words may be badly spelled as I wrote this when I first started learning!)|
|Example Audio File (Italiano)||Pimsleur - Italian I - Lesson 01.mp3 (11146.99 kB - downloaded 297 times.) (Legal notice at end of this post.)|
|Donate (Via DonationCoder)||Donate via Donationcoder|
|Donate (Via PayPal)||Donate via PayPal|
|Donation Notes||All donations will go towards buying coffee so I can be awake to add more cool stuff to AudioMarker (and I'll probably buy the mrs something for being patient whilst I code!)|
|Author||Click my name on this post|
Forward Why Would Anyone Learn This Stuff?
Amazing! You're actually reading this. That puts you into one of three categories: a student who is being forced to read this stuff for a class someone who picked up this book by accident (probably because you have yet to be indoctrinated by the world at large) or one of the few who actually have an interest in learning assembly language.
Egads. What kind of book begins this way? What kind of author would begin the book with a forward like this one? Well the truth is I considered putting this stuff into the first chapter since most people never bother reading the forward. A discussion of what's right and what's wrong with assembly language is very important and sticking it into a chapter might encourage someone to read it. However I quickly found that university students can skip Chapter One as easily as they can skip a forward so this stuff wound up in a forward after all.
So why would anyone learn this stuff anyway? Well there are several reasons which come to mind:
Your major requires a course in assembly language; i.e. you're here against your will.
A programmer where you work quit. Most of the source code left behind was written in assembly language and you were elected to maintain it.
Your boss has the audacity to insist that you write your code in assembly against your strongest wishes.
Your programs run just a little too slow or are a little too large and you think assembly language might help you get your project under control.
You want to understand how computers actually work.
You're interested in learning how to write efficient code.
You want to try something new.
Well whatever the reason you're here welcome aboard. Let's take a look at the subject you're about to study.
1. WHAT'S WRONG WITH ASSEMBLY LANGUAGE
Assembly language has a pretty bad reputation. The common impression about assembly language programmers today is that they are all hackers or misguided individuals who need enlightenment. Here are the reasons people give for not using assembly:
Assembly is hard to learn.
Assembly is hard to read and understand.
Assembly is hard to debug.
Assembly is hard to maintain.
Assembly is hard to write.
Assembly language programming is time consuming.
Improved compiler technology has eliminated the need for assembly language.
Today machines are so fast that we no longer need to use assembly.
If you need more speed you should use a better algorithm rather than switch to assembly language.
Machines have so much memory today saving space using assembly is not important.
Assembly language is not portable.
Python. Client side.
Skulpt is an entirely in-browser implementation of Python.
No preprocessing, plugins, or server-side support required, just write Python and reload.
The code is run entirely in your browser, so don't feel obligated to "crash the server", you'll only stub your toe. Help, or examples: 1 2 3 4 5 6 7 8. Ctrl-Enter to run.
This is a version adapted by Quentin Carbonneaux from David Evans' original document. The syntax was changed from Intel to AT&T, the standard syntax on UNIX systems, and the HTML code was purified.
This guide describes the basics of 32-bit x86 assembly language programming, covering a small but useful subset of the available instructions and assembler directives. There are several different assembly languages for generating x86 machine code. The one we will use in CS421 is the GNU Assembler (gas) assembler. We will uses the standard AT&T syntax for writing x86 assembly code.
The full x86 instruction set is large and complex (Intel's x86 instruction set manuals comprise over 2900 pages), and we do not cover it all in this guide. For example, there is a 16-bit subset of the x86 instruction set. Using the 16-bit programming model can be quite complex. It has a segmented memory model, more restrictions on register usage, and so on. In this guide, we will limit our attention to more modern aspects of x86 programming, and delve into the instruction set only in enough detail to get a basic feel for x86 programming.
Modern (i.e 386 and beyond) x86 processors have eight 32-bit general purpose registers, as depicted in Figure 1. The register names are mostly historical. For example, EAX used to be called the accumulator since it was used by a number of arithmetic operations, and ECX was known as the counter since it was used to hold a loop index. Whereas most of the registers have lost their special purposes in the modern instruction set, by convention, two are reserved for special purposes — the stack pointer (ESP) and the base pointer (EBP).
For the EAX, EBX, ECX, and EDX registers, subsections may be used. For example, the least significant 2 bytes of EAX can be treated as a 16-bit register called AX. The least significant byte of AX can be used as a single 8-bit register called AL, while the most significant byte of AX can be used as a single 8-bit register called AH. These names refer to the same physical register. When a two-byte quantity is placed into DX, the update affects the value of DH, DL, and EDX. These sub-registers are mainly hold-overs from older, 16-bit versions of the instruction set. However, they are sometimes convenient when dealing with data that are smaller than 32-bits (e.g. 1-byte ASCII characters).
Welcome to PyBrain
PyBrain is a modular Machine Learning Library for Python. Its goal is to offer flexible, easy-to-use yet still powerful algorithms for Machine Learning Tasks and a variety of predefined environments to test and compare your algorithms.
PyBrain is short for Python-Based Reinforcement Learning, Artificial Intelligence and Neural Network Library. In fact, we came up with the name first and later reverse-engineered this quite descriptive "Backronym".
How is PyBrain different?
While there are a few machine learning libraries out there, PyBrain aims to be a very easy-to-use modular library that can be used by entry-level students but still offers the flexibility and algorithms for state-of-the-art research. We are constantly working on more and faster algorithms, developing new environments and improving usability.
What PyBrain can do
PyBrain, as its written-out name already suggests, contains algorithms for neural networks, for reinforcement learning (and the combination of the two), for unsupervised learning, and evolution. Since most of the current problems deal with continuous state and action spaces, function approximators (like neural networks) must be used to cope with the large dimensionality. Our library is built around neural networks in the kernel and all of the training methods accept a neural network as the to-be-trained instance. This makes PyBrain a powerful tool for real-life tasks.
PyBrain is open source and free to use for everyone (it is licensed under the BSD Software Licence). Just download it and start using the algorithms and modules in your own project or have a look at the provided tutorials and examples. If you use PyBrain for your research, we kindly ask you to cite us in your publications. Use the reference below or import this bibtex reference.
This is a minimal crash-course in the programming language Python. To learn more, take a look at the documentation at the Python web site, www.python.org; especially the tutorial. If you wonder why you should be interested, check out the comparison page where Python is compared to other languages.
This introduction has been translated into several languages, among them Portuguese, Italian, Spanish, Russian, French, Lithuanian, Japanese, German and Greek, and is currently being translated into Norwegian, Polish, and Korean. Since this document still might undergo changes, these translations may not always be up to date.
Note: To get the examples working properly, write the programs in a text file and then run that with the interpreter; do not try to run them directly in the interactive interpreter - not all of them will work. (Please do not ask me for details on this! I get swamped with emails on the subject… Check the documentation, or send an email to [email protected]).
To begin with, think of Python as pseudo-code. It’s almost true. Variables don’t have types, so you don’t have to declare them. They appear when you assign to them, and disappear when you don’t use them anymore. Assignment is done by the = operator. Equality is tested by the == operator. You can assign several variables at once:
x,y,z = 1,2,3
first, second = second, first
a = b = 123
Blocks are indicated through indentation, and only through indentation. (No BEGIN/END or braces.) Some common control structures are:
if x < 5 or (x > 10 and x < 20):
print "The value is OK."
if x < 5 or 10 < x < 20:
print "The value is OK."
for i in [1,2,3,4,5]:
print "This is iteration number", i
x = 10
while x >= 0:
print "x is still not negative."
x = x-1
The first two examples are equivalent.
The index variable given in the for loop iterates through the elements of a list (written as in the example). To make an “ordinary” for loop (that is, a counting loop), use the built-in function range().
# Print out the values from 0 to 99 inclusive.
for value in range(100):
(The line beginning with “#” is a comment, and is ignored by the interpreter.)
Okay; now you know enough to (in theory) implement any algorithm in Python. Let’s add some basic user interaction. To get input from the user (from a text prompt), use the builtin function input.
x = input("Please enter a number: ")
print "The square of that number is", x*x
The input function displays the prompt given (which may be empty) and lets the user enter any valid Python value. In this case we were expecting a number — if something else (like a string) is entered, the program would crash. To avoid that we would need some error checking. I won’t go into that here; suffice it to say that if you want the user input stored verbatim as a string (so that anything can be entered), use the function raw_input instead. If you wanted to convert the input string s to an integer, you could then use int(s).
Note: If you want to input a string with input, the user has to write the quotes explicitly. In Python, strings can be enclosed in either single or double quotes.
So, we have control structures, input and output covered — now we need some snazzy data structures. The most important ones are lists and dictionaries. Lists are written with brackets, and can (naturally) be nested:
BASIC EXCEL SKILLS
Now a days, any job requires basic Excel skills. These basic Excel skills are – familiarity with Excel ribbons & UI, ability to enter and format data, calculate totals & summaries thru formulas, highlight data that meets certain conditions, creating simple reports & charts, understanding the importance of keyboard shortcuts & productivity tricks. Based on my experience of training more than 5,000 students in various online & physical training programs, the following 6 areas form the core of basic Excel skills.
Excel is a massive application with 1000s of features and 100s of ribbon (menu) commands. It is very easy to get lost once you open Excel. So one of the basic survival skills is to understand how to navigate Excel and access the features you are looking for.