Locate the files: libc.a libm.a libstdc++.a in your/usr/lib hierarchy. I found libm.a and libc.a in/usr/lib/debug/usr/lib These come from the debug packages for the kernel.
Create symbolic links to them in the project directory: ln -s/usr/lib/debug/usr/lib/libm.a . ln -s/usr/lib/debug/usr/lib/libc.a . ln -s `g++ -print-file-name=libstdc++.a`
You now have three symbolic links to the static libraries
Linking to these must be performed by using the current directory as a load library path:
g++ -static-libgcc -L. -o example example.cpp
Then your problem is trying to match a human skeleton to the shape. If you know the curvature of the gradient at a particular point, you can eliminate some body parts. A head is mostly spherical and within a particular maximum/minimum, limbs and the torso are more cylindrical with a linear depth along one axis. Look for that linearity, and you could determine that is a limb and what direction it is aligned in.
Just saw a program today (C4 something in the UK. One of the problems with the walls in these towns, was that, while they were higher than the actual tsunami wave, the ground lost elevation by 1 to 2 metres due to the shock waves.
One part of the program had views of a tourist in a Japanese park during the earthquake. He was filming the liquification of the ground as well as cracks opening up in the ground and pathways - some cases as wide as nine inches - these were moving at 5-10 cm/second.
I might have seen the video of the wave coming over a wall, it just poured in round the bend, knocking over a tug or two. Since the camera-people were only two houses away, I'm guessing it was this one.
There are so many design philosophies out there - going way beyond whether you put the opening { on the same line as the function name or else. These are just fourteen I can recall:
o Separate dll's vs separate static libraries o Separate directories for each class o Separate header/source files for each class o Inheritance vs class member objects o inline functions or not o use of STL vs Boost vs own templates o multiple template class types o Use of smart pointers o enum's vs defines o The use of class identifiers before functions : ClassName::FuncCall( x, y ) vs FuncCall o use of virtual inheritance with multiple inheritance o hand-written Makefile vs Cmake vs qmake o private class members always, with accessor functions o The GUI and other libraries used: WXwidgets, Qt, SDL, X-windows
Each author may have any combination of these fourteen methods - so any project can be rolled in at least 16000+ different ways.
C++ and parallelization don't seem to be mutually exclusive. It's fairly easy to write a C++ wrapper around pthreads, so you have a class container for all the data, one or more functions to process a single thread task, and a single function call to scatter the data, assign and supervise so-many threads to the task and gather the data afterwards.
Going back to that point is like winding the universe backwards towards the big-bang. As you collect everything into one point, all the energy in the form of photons and particle radation is going to heat everything up to the point it is ionized gas. Go to an even smaller volume and the nucleii themselves would break down into what the astronomers call a "quark soup". Forces such as gravity would cease to exist.
Its been proved that the electromagnetic and weak interaction forces are two aspects of the same electro-weak force, and would unify at high energies when the temperature is above 10^15Kelvin.
If space-time can "stretch" in the presence of a large amount of mess, then maybe it was crinkly in the first place? Presumably every atomic nucleus stretches a miniscule area of space-time around it, it's only really noticable to us as gravity when bundled together into planet sized objects.
And a 20m tsunamis wall didn't stop the water either. If you've got a wave 2000m long and 1m high, then all that water is just going to build up until it does go over the wall. The only other solution seems to be to build everything on stilts or build tsunamis channels that direct the water upwards and inland much like the opposite of a storm drain or storm channel.
They aren't cutting out entire blocks of ASIC circuitry in a Boolean keep or remove decision. They are sacrificing precision by reducing transistor count, and doing so in a somewhat heuristic approach in order to limit the loss of precision. Their algorithm will explore the worst case and best case of each arithmetic operation in order to achieve this. Not too different from the MiniMax approach to playing Chess or other board games.
The UK has off-peak electricity (white meters), while the regular-rate electricity goes through the standard meter (black meter). It usually means that people run their dish washers, washing machines and dryers in the early hours of the morning, and cook their evening meal after 6.00pm.
Smart meters in the UK let you know how many Kilowatts of electricity you are using at any moment, which encourages home-owners to switch off lights or to purchase dual motion-sensor/dimmer switches. One setting has the light off, another has the light on only if there is motion, and the third has the light permanently on.
There are Power station ships, but given the power requirements of Japan, they would need 30 of these.
Though it looks like the future is going to be Modular nuclear reactors, which are smaller than the conventional 3 GigaWatt reactor, but can be strung together and transported by container.
Worked as intern on a IT support help-desk many years ago. During quiet times, we'd do inventory on the RS232 breakout boxes and the LAN adapter cards, until someone called in to ask how to replace the paper on their laser printer. During crisis time, the help-desk operators would get calls from users if we knew the network had gone down, then the world would go crazy.
Early PC network cards had a habit of frying their MAC address EEPROMS and there weren't any internal firewalls at the time, so one PC could jam a whole office block.
I read about that - there was a book about Vimanas which claimed to be translated from ancient Sanskrit documents. It was fascinating read at a sci-fi/steampunk level as the technology described was more basic physics than anything way out there:
o Tinted windows to screen against infra-red / UV light to avoid annoying glare - at the time I read this book, the windows on our office block were actually laminated with blue/purple plastic to do this exact task.
o A pair of parabolic dishes to amplify sound to detect other systems. o Colored oils and a light projector to project images of lions, tigers, skulls on surfaces to scare the natives. o Shaped pipes (wider at the bottom than the top) and hot wires to create a propulsion system (like those hot wire standing wave pipe experiments) o Recessed cylinders along the side of the craft with propellers to create a stabilisation system o Releasabe fireworks/dyes to create camouflage smoke trails o Phosphorus screens, lenses and crystals to detect buried explosives (rays would be emitted, then reflected back to illuminate the phosphorus screen). I wondered if that would be some kind of X-ray emission/UV absorption system
Really wonder how many of these actually would work...
It's well known from archived archeological papers and ancient manuscripts dating from the Roman era, that around 3 miles (5 km) of farmland around some areas has disappeared into the sea since Roman times. You only need to erode 2.5 metres/year on average to achieve this rate of loss. Even just having one bad storm that erode 10 metres in a single night, once every 10 years is enough to achieve this.
Even if Atlantis never existed, there is a good chance that any point of ocean bed is going to having artifacts from sunken ships, islands or even tsunamis.
As one detective once said, "Every dumb criminal is a failure of the education system."
Like the kind who go house-burglaring during a snowstorm thinking that the bilzzard of snowflakes will camouflage them against the surroundings. Then the detectives just follow the footprints in the snow from the crime scene back to their home.
Those are just mathematical buzzwords which are easy to to understand once you know what they mean. I know your plight, I'm trying to learn Blender in order to generate some geometric objects. It's easier for me to draw a wireframe shape on paper, number the vertices and write out the triangle face lists than it is too figure out edit mode in Blender.
You should look at the current jobs market. All of the good paying jobs require solid mathematics knowledge, especially for anything simulation/visualization related - CFD, aerodynamics, combustion systems, design/simulation of industrial processing equipment (grinders, shredders, slicers), and require OpenGL, CUDA, MPI, OpenMP experience as well.
Those jobs that aren't mathematics related, seem to be more arts based (web design) requiring knowledge of Photoshop, 3Dmax. The remainder seems to be management or customer facing roles.
At the started of the 3D graphics chip race, there were 30+ competitiors. 3Dlabs, Nvidia, 3dfx, ATI, Lockheed-Martin, HP, IBM, and many others... Once the hardware became more complicated and the patents started flying, this was reduced down to a handful. Though, there seems to be resurgence of mobile device manufacturers using OpenGL-ES.
Microsoft provides far more direct developer support for DirectX along with developer forums and developing console systems. That makes all the difference to developers.
Then SGI employed Brian Hook to port OpenGL to PC's to show that a software implementation of OpenGL could be as fast as a software based game engine of the time.
Tesla Power is a fascinating on-the-edge-of science topic to read about, related to Schumann resonances . Like a giant Tesla coil, the atmosphere acts as an electronmagnetic resonance cavity bounded by the surface and the ionosphere with resonance frequencies starting at 7.5Hz, and upwards.
Demon Internet did that for us in the UK. One floppy disk provided an integrated MSDOS application to handle E-mail and USENET articles. Utilities like FTP, telnet, gopher, whois, ping all came as command line commands. Only needed a 14.4K modem and PPP/Winsock that ran on a 20MHz 386 PC. The introductory pack came with a original deed title ownership of an internet domain name and static IP address.
We did have the Wapping Dispute in 1986, where displaced print workers went on strike to protest about the replacement of their jobs with new technology and with no retraining. The problem was there wasn't anywhere for them to be retrained - they couldn't do journalism, or do print delivery. All the metalwork, typesetting and stripping was replaced by a document system, LAN and some industrial laser printers. They proposed that they would do the transcription of journalist shorthand into the computer, but the journalists were already being trained to do the keyboarding.
Back in the 1980's, we knew the coming microprocessor revolution was coming. There were books like "The Coming of the Chip" by Anthony Hyman and "The Computer Revolution". The BBC also had a debate called "When the Chips are Down". The focus of all these publications were about how so many manual labour jobs were going to be replaced by automation. The obvious jobs were car manufacturing, component assembly lines where repetitive tasks would be replaced by robots. Other prohecies were that secretaries would no longer be needed as we wouldn't need typewriters. In part, that was true, but they took on other duties, and became admins or executaries instead. Later documentaries covered how places like Singapore were using AI to remain competitive in the shipping industry by placing crates in the most suitable location in the hold of a cargo container ship. Universities started using AI to draw up the department and faculty lecture timetables. Other predictions were the "paperless office", where there would be no need for printed documents as everything would be sent by E-mail. Yet, at the same time, laser printers and WYSIWYG printing became standard.
Now even code generation is being done automatically using Python/Perl scripts - things like GLEW and Qt's Designer. In the end, the only real two jobs left are the API R&D and the application developer who binds the API calls to the application user-interface.
Slashdot Mirror
Those will be the tech sectors that can afford to employ engineers at the lowest rates:
Net Profit = Gross Profits - (Estate costs + R&D costs + adminstration costs + raw-materials + distribution costs)
You need to do the following:
Locate the files: libc.a libm.a libstdc++.a in your /usr/lib hierarchy. /usr/lib/debug/usr/lib
I found libm.a and libc.a in
These come from the debug packages for the kernel.
Create symbolic links to them in the project directory:
/usr/lib/debug/usr/lib/libm.a . /usr/lib/debug/usr/lib/libc.a .
ln -s
ln -s
ln -s `g++ -print-file-name=libstdc++.a`
You now have three symbolic links to the static libraries
Linking to these must be performed by using the current directory as a load library path:
g++ -static-libgcc -L. -o example example.cpp
Then test using 'ldd'
ldd example
not a dynamic executable
The function: f=d(x+u/d(x))-d(x+v/d(x)) would calculate the depth gradient of the pixel. It's possible to reconstruct a three dimensional shape from a 2D image .
Then your problem is trying to match a human skeleton to the shape. If you know the curvature of the gradient at a particular point, you can eliminate some body parts. A head is mostly spherical and within a particular maximum/minimum, limbs and the torso are more cylindrical with a linear depth along one axis. Look for that linearity, and you could determine that is a limb and what direction it is aligned in.
Just saw a program today (C4 something in the UK. One of the problems with the walls in these towns, was that, while they were higher than the actual tsunami wave, the ground lost elevation by 1 to 2 metres due to the shock waves.
One part of the program had views of a tourist in a Japanese park during the earthquake. He was filming the liquification of the ground as well as cracks opening up in the ground and pathways - some cases as wide as nine inches - these were moving at 5-10 cm/second.
I might have seen the video of the wave coming over a wall, it just poured in round the bend, knocking over a tug or two. Since the camera-people were only two houses away, I'm guessing it was this one.
There are so many design philosophies out there - going way beyond whether you put the opening { on the same line as the function name or else. These are just fourteen I can recall:
o Separate dll's vs separate static libraries
o Separate directories for each class
o Separate header/source files for each class
o Inheritance vs class member objects
o inline functions or not
o use of STL vs Boost vs own templates
o multiple template class types
o Use of smart pointers
o enum's vs defines
o The use of class identifiers before functions : ClassName::FuncCall( x, y ) vs FuncCall
o use of virtual inheritance with multiple inheritance
o hand-written Makefile vs Cmake vs qmake
o private class members always, with accessor functions
o The GUI and other libraries used: WXwidgets, Qt, SDL, X-windows
Each author may have any combination of these fourteen methods - so any project can be rolled in at least 16000+ different ways.
you know, for the folks that never understood what a memory leak is.
It's like wikileaks, but with memristors instead of wikis
C++ and parallelization don't seem to be mutually exclusive. It's fairly easy to write a C++ wrapper around pthreads, so you have a class container for all the data, one or more functions to process a single thread task, and a single function call to scatter the data, assign and supervise so-many threads to the task and gather the data afterwards.
Going back to that point is like winding the universe backwards towards the big-bang. As you collect everything into one point, all the energy in the form of photons and particle radation is going to heat everything up to the point it is ionized gas. Go to an even smaller volume and the nucleii themselves would break down into what the astronomers call a "quark soup". Forces such as gravity would cease to exist.
Its been proved that the electromagnetic and weak interaction forces are two aspects of the same electro-weak force, and would unify at high energies when the temperature is above 10^15Kelvin.
If space-time can "stretch" in the presence of a large amount of mess, then maybe it was crinkly in the first place? Presumably every atomic nucleus stretches a miniscule area of space-time around it, it's only really noticable to us as gravity when bundled together into planet sized objects.
There was guy who was .
And a 20m tsunamis wall didn't stop the water either. If you've got a wave 2000m long and 1m high, then all that water is just going to build up until it does go over the wall. The only other solution seems to be to build everything on stilts or build tsunamis channels that direct the water upwards and inland much like the opposite of a storm drain or storm channel.
They aren't cutting out entire blocks of ASIC circuitry in a Boolean keep or remove decision. They are sacrificing precision by reducing transistor count, and doing so in a somewhat heuristic approach in order to limit the loss of precision. Their algorithm will explore the worst case and best case of each arithmetic operation in order to achieve this. Not too different from the MiniMax approach to playing Chess or other board games.
The UK has off-peak electricity (white meters), while the regular-rate electricity goes through the standard meter (black meter). It usually means that people run their dish washers, washing machines and dryers in the early hours of the morning, and cook their evening meal after 6.00pm.
Smart meters in the UK let you know how many Kilowatts of electricity you are using at any moment, which encourages home-owners to switch off lights or to purchase dual motion-sensor/dimmer switches. One setting has the light off, another has the light on only if there is motion, and the third has the light permanently on.
How about some mobile nuclear reactors, or as Wired titled an article:
In Soviet Union, nuclear reactors finds you!
Russian mobile nuclear reactors
There are Power station ships, but given the power requirements of Japan, they would need 30 of these.
Though it looks like the future is going to be Modular nuclear reactors, which are smaller than the conventional 3 GigaWatt reactor, but can be strung together and transported by container.
Worked as intern on a IT support help-desk many years ago. During quiet times, we'd do inventory on the RS232 breakout boxes and the LAN adapter cards, until someone called in to ask how to replace the paper on their laser printer. During crisis time, the help-desk operators would get calls from users if we knew the network had gone down, then the world would go crazy.
Early PC network cards had a habit of frying their MAC address EEPROMS and there weren't any internal firewalls at the time, so one PC could jam a whole office block.
I read about that - there was a book about Vimanas which claimed to be translated from ancient Sanskrit documents.
It was fascinating read at a sci-fi/steampunk level as the technology described was more basic physics than anything way out there:
o Tinted windows to screen against infra-red / UV light to avoid annoying glare - at the time I read this book, the windows on our office block were actually laminated with blue/purple plastic to do this exact task.
o A pair of parabolic dishes to amplify sound to detect other systems.
o Colored oils and a light projector to project images of lions, tigers, skulls on surfaces to scare the natives.
o Shaped pipes (wider at the bottom than the top) and hot wires to create a propulsion system (like those hot wire standing wave pipe experiments)
o Recessed cylinders along the side of the craft with propellers to create a stabilisation system
o Releasabe fireworks/dyes to create camouflage smoke trails
o Phosphorus screens, lenses and crystals to detect buried explosives (rays would be emitted, then reflected back to illuminate the phosphorus screen). I wondered if that would be some kind of X-ray emission/UV absorption system
Really wonder how many of these actually would work...
It's well known from archived archeological papers and ancient manuscripts dating from the Roman era, that around 3 miles (5 km) of farmland around some areas has disappeared into the sea since Roman times. You only need to erode 2.5 metres/year on average to achieve this rate of loss. Even just having one bad storm that erode 10 metres in a single night, once every 10 years is enough to achieve this.
Even if Atlantis never existed, there is a good chance that any point of ocean bed is going to having artifacts from sunken ships, islands or even tsunamis.
As one detective once said, "Every dumb criminal is a failure of the education system."
Like the kind who go house-burglaring during a snowstorm thinking that the bilzzard of snowflakes will camouflage them against the surroundings. Then the detectives just follow the footprints in the snow from the crime scene back to their home.
Those are just mathematical buzzwords which are easy to to understand once you know what they mean. I know your plight, I'm trying to learn Blender in order to generate some geometric objects. It's easier for me to draw a wireframe shape on paper, number the vertices and write out the triangle face lists than it is too figure out edit mode in Blender.
You should look at the current jobs market. All of the good paying jobs require solid mathematics knowledge, especially for anything simulation/visualization related - CFD, aerodynamics, combustion systems, design/simulation of industrial processing equipment (grinders, shredders, slicers), and require OpenGL, CUDA, MPI, OpenMP experience as well.
Those jobs that aren't mathematics related, seem to be more arts based (web design) requiring knowledge of Photoshop, 3Dmax. The remainder seems to be management or customer facing roles.
At the started of the 3D graphics chip race, there were 30+ competitiors. 3Dlabs, Nvidia, 3dfx, ATI, Lockheed-Martin, HP, IBM, and many others ... Once the hardware became more complicated and the patents started flying, this was reduced down to a handful. Though, there seems to be resurgence of mobile device manufacturers using OpenGL-ES.
Microsoft provides far more direct developer support for DirectX along with developer forums and developing console systems. That makes all the difference to developers.
Then SGI employed Brian Hook to port OpenGL to PC's to show that a software implementation of OpenGL could be as fast as a software based game engine of the time.
Arthur C Clarke wrote a story about the Cheela in "Dragon's Egg?" Due to the strong gravitational field, they are only something like 5mm high.
Fascinating that in the gravity of a real neutron star, the atmosphere is going to be less that half a metre in height.
Tesla Power is a fascinating on-the-edge-of science topic to read about, related to Schumann resonances . Like a giant Tesla coil, the atmosphere acts as an electronmagnetic resonance cavity bounded by the surface and the ionosphere with resonance frequencies starting at 7.5Hz, and upwards.
Demon Internet did that for us in the UK. One floppy disk provided an integrated MSDOS application to handle E-mail and USENET articles. Utilities like FTP, telnet, gopher, whois, ping all came as command line commands. Only needed a 14.4K modem and PPP/Winsock that ran on a 20MHz 386 PC. The introductory pack came with a original deed title ownership of an internet domain name and static IP address.
We did have the Wapping Dispute in 1986, where displaced print workers went on strike to protest about the replacement of their jobs with new technology and with no retraining. The problem was there wasn't anywhere for them to be retrained - they couldn't do journalism, or do print delivery. All the metalwork, typesetting and stripping was replaced by a document system, LAN and some industrial laser printers. They proposed that they would do the transcription of journalist shorthand into the computer, but the journalists were already being trained to do the keyboarding.
Back in the 1980's, we knew the coming microprocessor revolution was coming. There were books like "The Coming of the Chip" by Anthony Hyman and "The Computer Revolution". The BBC also had a debate called "When the Chips are Down". The focus of all these publications were about how so many manual labour jobs were going to be replaced by automation. The obvious jobs were car manufacturing, component assembly lines where repetitive tasks would be replaced by robots. Other prohecies were that secretaries would no longer be needed as we wouldn't need typewriters. In part, that was true, but they took on other duties, and became admins or executaries instead. Later documentaries covered how places like Singapore were using AI to remain competitive in the shipping industry by placing crates in the most suitable location in the hold of a cargo container ship. Universities started using AI to draw up the department and faculty lecture timetables. Other predictions were the "paperless office", where there would be no need for printed documents as everything would be sent by E-mail. Yet, at the same time, laser printers and WYSIWYG printing became standard.
Now even code generation is being done automatically using Python/Perl scripts - things like GLEW and Qt's Designer. In the end, the only real two jobs left are the API R&D and the application developer who binds the API calls to the application user-interface.