Learn How to Trade Binary Options Online (Free Binary

Sympathy for the Drow - De-Vilifying the Dark Elves

The "Evil" races in DnD have always rubbed me kinda the wrong way. Partly once I learned that a lot of them come from racist stereotypes (Orcs, Drow, and Goblins in particular) and also just because it doesn't make sense to me. Even Nazi Germany had variation and dissenters and it only lasted for 12 years. Why would a clearly evil society never change over hundreds of years? In my opinion, a story is only as good as it's villains. So, I've set out to try and make the traditionally evil races slightly more believable and even sympathetic in places.
Now, I've not been a DM very long, only like three years. But the first campaign I ever ran was through Curse of Strahd which paints the Vistani (an itinerant society heavily based on the real world Romani) as a conniving group of thieves, murders, and vampire-worshipers. Thankfully, I found through reddit and other sites how to steer away from the racists depictions of the Vistani and making them seem like, at worst, opportunists. So, I hope to be able to do that with some other of the classic DnD antagonist races.
I've read some other phenomenal post on here about evil races that totally inspired me as well. There's a great two part post about Decolonizing D&D which I adore. The post about alignment is easily my favorite. There's a couple great ones on Orcs and Yuan-Ti too so if some of my ideas are lifted from them, I hope y'all consider it flattery instead of theft. So, here are some primer notes before I get into it.
For creating the Dark Elves, I tried to keep as much as I could from the books. Obviously some stuff has to get thrown out the window though. I also tried to standardize calling them Dark Elves instead of Drow partly because I feel like Drow has a much nastier sound to it and calling them Dark Elves follows the naming convention with the High and Wood Elves. I tried to model them after real-life matriarchal societies like the Mosuo people of China and their pantheon after real deities like the Greeks, Romans, and Norse. I also quickly realized that building a society is inseparable from geography. Where a people are from effects their language, values, mythology, history, and family structure. I've tried to outline details I think are necessary to making this society realistic while leaving it open ended enough to be place-able in different worlds with relative ease. All that aside, lets get into the meat of it.

The Dark Elves: Elven Outcasts

The Elves are a varied and magical people that come from many planes and many environments within them. But none are met with more distrust and fear than the Dark Elves. Easily set apart from their cousins by their charcoal or pitch-black skin, pink-red eyes, hair of grays and whites, and shorter stature, these people have earned a reputation as killers, thieves, demon worshipers, and liars. But history is a cruel mistress, something the Dark Elves know better than most.

The Divine Divide

As the legends go, when the world was still young, Corellon Larethian lived on the Plane of Arvandor with his fellow Primal Elves. They were wild and mutable, emotional and free in all things. They changed shapes at will, gave and took freely to and from the world, and never stayed in any location too long. They wandered to and fro, scattering their peoples across almost every plane. However, this unbridled freedom was not without a price. Arguments, feuds, and small scale wars were incredibly common between them. Some elves would find themselves stranded on far off planes after most of their companions impulsively decided to leave. Their self serving impulses drove them to often completely disregard the needs or wants of others if they went against their own desires. And their reckless revelry was wreaking havoc on the natural world with Elven parties decimating whole planes of edible plants, wild game, and drinkable water.
One such Primal Elf began to see the destruction of their ways and talked to other elves about their actions. Slowly, this Elf by the name of Lolth amassed a small following of devotees that saw the negative ramifications of their inconsiderate freedom. Lolth and her followers agreed to take on fixed forms to show recognition of the dangers that impulsivity could bring. Lolth led this small group of devotees to Corellon to ask for his support. Now, Corellon did not lead these Primal Elves: he was just as wild as the best of them and did not take kindly to others telling him what to do. But he was the First Elf ever born and was universally respected amongst the Primal Elves and if Lolth could convince him, others would surely follow. Corellon listened to her proposition and agreed that they should change to prevent more destruction and conflict, but refused to order his kinsfolk into any action. He was an Elf, same as all of them, and he wouldn’t dare order around his family. He balked when Lolth asked him to take a concrete form as a show of solidarity and brushed her off as a killjoy.
Lolth was unsatisfied with this outcome and her following set out to convince each Elf to change their ways to preserve the beauty of the worlds. However, without the support of Corellon, many elves refused her offer. Her anger grew with each failure and her opinion of Corellon turned sour, something she made no attempt to hide from her Elven siblings. Now, Corellon is a proud god and once he caught wind that Lolth was bad mouthing him in an attempt to win over others, he became enraged. He railed against Lolth calling her a snake-tongued thief and Lolth called him incompetent and cruel. Their tempers flared and all the elves chose sides between Corellon’s freedom and Lolth’s stability. During this great debate, the Primal Elves turned to violence. The Dark Elves maintain that Corellon’s side threw the first blow, while the High Elves claim that it came from Lolth’s side.
No matter the source, this violent outburst soured relations between Lolth and Corellon forever after. He cast her and her followers out of Arvandor and barred her from ever returning. He also cast all but his most trusted kin from Arvandor, forcing them all to live lives on other worlds out of fear of another perceived insurrection. Thus, the Seldarine remain in Arvandor to judge the souls of Corellon’s faithful when they die and Lolth takes refuge in Arcadia with her pantheon where she minds the souls of the Drow. Corellon’s faithful call her pantheon the Dark Seldarine, while her faithful call it the Myrkalfar.

Myrkalfar: The Spider Mother’s House

Lolth the Spider Queen is the unquestioned head of the Myrkalfar, with all other deities seen as her divine family. Lolth is considered at times to be fickle or even cruel, but her ire is never gained without good reason. A very involved deity, her followers constantly search for signs of her favor or scorn in everyday life. When a Dark Elf contemplates a risky or controversial decision, they consult priestesses or perform their own rites which often gives them direct and succinct answers. She serves as an example to matriarchs of Drow families as demanding yet understanding, punishing yet guiding. She asks for a lot of her priestesses, demanding they be an unflinching example of everything a strong leader should be. The Myrkalfar is often presented as a divine household, with Lolth as the matron.
Keptolo is the consort of Lolth and considered to be the ideal of what a male should be. Beautiful and kind, strong and hard working, he helps Lolth in everything she does. Sometimes he serves as a messenger, other times as an agent of redemption, sometimes as a divine healer. When a Dark Elf is tasked with a divine charge, he is usually the one to deliver the message and guide them through their charge. He serves also as a fertility deity and is often worshiped by women or men seeking a child. Outsiders see him as a weak and subservient husband to Lolth, but his faithfulness to his matron is considered a virtue and his status as a “husband” is relatively alien to the Dark Elves as they have no binding marriage in their society.
If Keptolo is the agent of Lolth’s mercy, Kiaransalee is the agent of her vengeance. She is the eldest daughter of Lolth and Keptolo and one that Dark Elves pray to when they feel wronged. Only the most binding and serious contracts are signed under her name. To break an oath made under her name is sure to bring destruction. She is also the governor of the dead, judging the souls of those passed in the afterlife. She opposes the mindless undead created by mortals, but spirits and revenants that return to finish unresolved business amongst the living are considered under her protection. Should a Dark Elf encounter a returned spirit that is seeking vengeance, it’s their duty to leave them on their way and pray that the spirit isn’t there for them. This reverence of certain undead is something many outsiders consider downright evil.
Selvetarm is the Dark Elven warrior goddess and youngest daughter of Lolth. Often depicted with eight arms, she represents the pinnacle of hand to hand martial prowess, but often is without restraint. She serves as both an inspiration for warriors, and a warning. Vhaeraun is the eldest son of Lolth and governs ambition and stealth. Both of these traits are not necessarily vilified, but worship of him is highly scrutinized. Haughty and rash, tales of him often include deceiving his fellow gods for good and ill and more often than not are cautionary ones. He’s depicted as wearing a mask, either as some punishment for endangering Lolth and her family or to hide his identity for various schemes, possibly both.
Malyk is Lolth’s youngest son and a youthful deity of change and growth. He’s often seen as a bouncing young boy that Lolth and her family have to reign in from wild misadventures. His freedom and curiosity is often seen as a double edged sword, both gaining him great riches but also putting him in tremendous peril. He has strong ties to sorcerers and when a child is born with innate magical talent, he is often the one thanked for it. He serves as an outlet for a Dark Elves youthful chaotic nature, but also warns them of the ramifications of their actions.
Ghaunadur is a strange figure in the pantheon. Their place in the family is a bit of a mystery, sometimes called the sibling of Lolth, or her child, or even as Lolth’s parent. What makes them truly unique is that they are a formless deity, something that Lolth once warred with Corellon over. The legends go that when Ghaunadur joined Lolth, they refused to give up their changeable nature. When questioned, Ghaunadur pointed to the slimes, oozes, and formless creatures of the world and said that they wished to protect them from the Elves and the Elves from them. Lolth agreed, cementing their position as the deity of the changing forms of nature. Their favored creature is the ooze, but they govern all natural creatures. Dark Elves often pray to Ghaunadur to protect them from the creatures that lurk in the depths of the forest.
Zinzerena is Lolth’s sister and is the goddess of poisons, illusions, and magic. Viewed as an elderly and patient figure, she often serves as council to Lolth in desperate times. She’s said to be the mother of all poisons and venoms and her teachings are all about finding the wisest solution to a problem. Zinzerena teaches that even though the spider is small, it’s bite can still fell a panther. Despite her perceived age, she’s considered the younger sister of Lolth and is thought to be incredibly quick and nimble: a reminder that not everything is as it seems.
Eilistraee is Lolth’s niece and daughter of Zinzerena. Considered the black sheep of the pantheon, she serves as a goddess of redemption and moonlight. Dark Elves that turn their back on their family or scorn traditions will sometimes find themselves turned to Driders, half-spider half-Dark Elf creatures shunned by all. Eilistraee is said to watch over these creatures and if they are repentant, offer them challenges that they could complete to redeem themselves. Lolth often views her with contempt or mistrust, but never hates her and maintains her place in the pantheon. Dark Elven faithful rarely worship her as the others. She’s also one of the only deities of the Myrkalfar to claim no animosity toward the Seldarine and their faithful.
Spiders are the sacred animal of Lolth and are often used as an example of social order and the importance of family bonds. Each strand of silk serves the web as whole. More literally, the giant spiders of the Underdark are multifaceted and incredibly useful creatures. Serving as beasts of burden, war steeds, meat producers, household guardians, and silk producers, they are present in almost every facet of society. Their silks are used in everything from wound dressings to armor to architecture. To kill or steal another family's spider is considered akin to stealing a member of the family. Smaller and more poisonous spiders are often kept in temples and their webs are used as divining tools for priestesses.

Elven Exiles

The recorded history of the Dark Elves is full of contradictions from High Elf and Dark Elf sources. What historians can agree on is when the Elves of the Prime Material arrived, the followers of Lolth secluded from their Wood and High cousins and retreated into the Azelarien, also known as the Green Sea in Common. A massive forest, nearly 1 million square miles of dense and vibrant trees, that grows denser and darker the farther in one ventures. For countless eons, the High, Wood, and Dark Elves lived in relative harmony in their own corner of the world. High Elves lived near the forests in towns and villages, the Wood Elves lived in the lightly forested outlands of the Green Sea, and the Dark Elves lived deep in the central forests which was so dense that very little light reached the forest floor.
As time passed and their villages turned to cities, the High Elves began expanding into the forest, chopping some down to build homes and heat their furnaces. This began pushing into the territory of the Wood Elves and eventually the Dark Elves as well. These two peoples formed a shaky alliance to push back the expansive tide of the far larger High Elven armies. This alliance proved successful however and the High Elven forces began losing ground. What happened next is a matter of some debate. High Elven historians attest that the Dark Elven armies used Wood Elven soldiers as unwitting bait to lure the High Elven armies into a trap, thus causing a schism between them. Dark Elven historians state that the Wood Elven armies turned on them after the Wood Elves met in secret with High Elven leaders and bargained for their independence. Some Wood Elven historians claim that after a brutal defeat on the field, they were met by High Elven dignitaries that offered them clemency if they turned on their allies. They initially refused, but after the dignitaries threatened to make the same offer to the Dark Elves, they had no choice but to accept. No matter the cause, the histories agree that the Wood Elves turned on their erstwhile allies and helped push the Dark Elves into a rapid loss of ground.
Facing the might of the two armies with their own relatively small one, the Dark Elves were beaten into a hasty retreat into their own territory. Losing every open encounter, the Dark Elf matrons developed a new strategy of combat. The armies switched from training as many as quickly as they could, to training only a select few in multiple different forms of combat and magic. As the High and Wood Elves advanced into their territory, they quickly found their supply lines cut out from under them, their soldiers ambushed while sleeping, their scouts captured, and their leaders assassinated. And even if they would make it to a Dark Elf settlement, they would find it abandoned and booby-trapped, warned by their fast and silent scouts. If the Dark Elves couldn’t face their enemies head-on, they would weaken them with quick and decisive strikes.
Eventually, the war ground to a stalemate. The High Elves couldn’t push into the Dark Elf territory far enough to capture any cities of note without taking severe casualties and the Dark Elves were only managing to hold the invading armies back and couldn’t muster a force strong enough to push back to the enemy capital. Thus, the war cooled into a tense peace. The leaders came together to draw borders, but neither side fully forgave nor forgot one another’s actions. High and Wood Elves viewed the change in tactics by the Dark Elves as an unethical violation of the standards of war. The Dark Elves felt a particular animosity toward the Wood Elves, considering them backstabbers in their darkest hour.

Dark Elf Families: Matrons of Order

The Dark Elf society, to an outsider, looks like an oppressive and cruel society of slave traders and backstabbers. But the truth is more subtle. The Dark Elves value tradition and filial piety above almost all else. To a Dark Elven citizen, their family name is their most valuable possession and they are taught from a very young age that to look after their parents and their younger siblings is the highest virtue. Ancestors that have achieved great things often have shrines in a household alongside the gods themselves. A Dark Elf going against the will of their family is considered one of the highest taboos and often causes them to be outcast from Dark Elven society as a whole. Dark Elf society is matrilineal meaning that the eldest woman in each family is revered as the household leader and receives great respect from her family and society. This also means that the males of the society don’t inherit wealth as frequently as the females.
Dark Elven families are quite large, often with multiple generations along with aunts, uncles, and cousins living in the same household. New children almost always reside with their mother. Males of the society are expected to care not for their own biological children, but for the children born to their sisters, aunts, or nieces. This results in a striking amount of sexual freedom for both men and women, but is often viewed from the outside as promiscuity. The Dark Elves do not marry in the traditional sense, instead favoring long term partners with one another that can end at any time with no concerns to material wealth or ownership.
However, to become a member of a Dark Elf family is not entirely a matter of heritage. When a family that cannot support another child has one, they are often adopted by more well to do families and raised as one of their own. These adopted children are considered just as legitimate as if they were born into the family. Also, should a family lose all their heirs or become destitute, they often ask to become assimilated into other families for their own safety. The latter is considered a morose ceremony as the members of the smaller family forsake their surnames. To take in such a family is both an extreme honor and grim burden, as it means ending another family's line.
The borders of Dark Elven civilization only goes so far as there are trees so many newer up and coming families have expanded underground, a difficult and slow endeavor. This has put multiple houses at odds with one another for territory. However, Dark Elves do not tolerate open hostility between families as they have a very strong sense of collective identity. Dark Elves do not war against fellow Dark Elves, same as a spider does not fight its own web. This leads to many tensions and conflicts needing to be resolved in other ways. Most families will attempt a diplomatic solution, but when that isn’t an option, sabotage and coercion is the favored outlet. Murder is considered a bridge too far by most houses, but subterfuge in almost every other facet is, while not accepted, tolerated.
Legends of Lolth’s rebellion and the tension of their enclosed territory have imbued the Dark Elves with a strong sense of symbiosis with nature and conservancy. Sustainable living is the cornerstone of Dark Elf society. In the wild, no creature is killed or plant destroyed unless it’s a matter of self defense or necessary to survival.

Dark Elven Sex and Gender

As with many Elven peoples, sexuality is seen as a fluid and non-binary matter. Same sex relationships are usually seen as just as acceptable as male-female relationships. Since Dark Elves have no marriage structure, same sex life partners are common and widely accepted. Inheritance is passed along by the family as a whole, not linearly, meaning some houses may have matrons with no direct biological descendants while still serving at the elder matron. Power dynamics in relationships are still a factor, with the elder female in a gay relationship considered slightly above their partner socially and is seen as the inheritor in cases of property or genealogy. Male same sex relationships are accepted with little controversy. Since children are passed down their mothers line, the males have no social obligation to sire an heir as with other societies.
Transgender and transexual Dark Elves are met with slightly more controversy. Lolth’s rejection of the Primal Elves mutable forms is sometimes cited against transgender and transexual Dark Elves. Ghaunadur, however, is considered the patron god of these people and teaches that just as they are part of nature, they can change their forms. Many of these people join the religious order of Ghaunadur, serving in various roles both in religious ceremonies and as forest guides. Some even consider them to be blessed by Ghaunadur and are highly sought after in forays into the forests for protection. Children born to transgender Dark Elves are still expected to be a part of their eldest mother’s family or eldest father if no woman is part of the union.

Slavery Amongst the Dark Elves

While the Dark Elves do take slaves, their slavery doesn’t look the same as many other societies. When a family becomes indebted to another and they cannot pay off the debt, a member of their family, usually male, will be sent to work for the owed family. They give him room and board and are expected to care for him as if he were one of their own. He’ll work for them for an agreed upon amount of time before returning to his native family. Injury or misuse of this person is often grounds for them to leave and the debt to be nullified. Children born to servant fathers needn’t worry about inheriting their father’s status since they’re considered to be their mother’s child. On the rare occasion that a female servant has a child while in servitude, the child is returned to the mother’s family to be raised by her family while she works off the remaining debt. Some trade of servants does occur between houses, with indentured servants being traded for goods or services or even other servants of special skills, but the family of the servant reserves the right to veto such a trade for any reason.
During their frequent clashes with external armies, the Dark Elves do sometimes take prisoners of war, though very rarely are they used for slave labor. They never bring them back to major settlements, often keeping them on the outskirts of their territory to prevent them from learning critical knowledge of their territory. Most prisoners are held as bargaining chips to be traded for passage, supplies, or captured Dark Elves. Captured military leaders are sometimes brought to Dark Elven cities to be tried for their crimes against their people.

Dark Elven Government: Independent Houses

Unlike many other cultures, the Dark Elves lack a centralized government. Societal etiquette govern the standard for how certain crimes and disagreements should be handled, but each family unit acts as its own governing body. Disagreements within families are thus resolved internally. Inter-family disputes are resolved in multiple different ways. Most often, the two matrons of the family will meet and agree on terms to fairly compensate both sides. In cases when these talks deteriorate, the High Priestess of Lolth is often called to serve as the mediator and serves as the ruling body between disputes. Her rulings are final and indisputable, as she is considered the mouthpiece of Lolth’s will.
In times of crisis, historically the many houses of the Dark Elves have convened to discuss threats to all of Dark Elven society. This is uncommon as it’s difficult logistically to gather all the matrons in the same place at the same time, so often houses are represented by either the second eldest woman of the family or the eldest daughter of the matron. The High Priestess of Lolth often resides over these meetings as an arbiter in the event of split decisions or in delivering guidance from Lolth herself.

There's my take on the Dark Elves. Any comments, suggestions, questions, outrages, and critiques are welcomed. This is my first comprehensive look at a whole race so if I've missed things, I'll try and patch them up. I'd like to do similar things for Orcs, Goblinoids, Kobolds, and others so those might be seen soon. Thanks!
submitted by Lerad to DnDBehindTheScreen [link] [comments]

Step-by-Step Guide for Adding a Stack, Expanding Control Lines, and Building an Assembler

After the positive response to my first tutorial on expanding the RAM, I thought I'd continue the fun by expanding the capabilities of Ben's 8-bit CPU even further. That said, you'll need to have done the work in the previous post to be able to do this. You can get a sense for what we'll do in this Imgur gallery.
In this tutorial, we'll balance software and hardware improvements to make this a pretty capable machine:

Parts List

To only update the hardware, you'll need:
If you want to update the toolchain, you'll need:
  1. Arduino Mega 2560 (Amazon) to create the programmer.
  2. Ribbon Jumper Cables (Amazon) to connect the Arduino to the breadboard.
  3. TL866 II Plus EEPROM Programmer (Amazon) to program the ROM.
Bonus Clock Improvement: One additional thing I did is replace the 74LS04 inverter in Ben's clock circuit with a 74LS14 inverting Schmitt trigger (datasheet, Jameco). The pinouts are identical! Just drop it in, wire the existing lines, and then run the clock output through it twice (since it's inverting) to get a squeaky clean clock signal. Useful if you want to go even faster with the CPU.

Step 1: Program with an Arduino and Assembler (Image 1, Image 2)

There's a certain delight in the physical programming of a computer with switches. This is how Bill Gates and Paul Allen famously programmed the Altair 8800 and started Microsoft. But at some point, the hardware becomes limited by how effectively you can input the software. After upgrading the RAM, I quickly felt constrained by how long it took to program everything.
You can continue to program the computer physically if you want and even after upgrading that option is still available, so this step is optional. There's probably many ways to approach the programming, but this way felt simple and in the spirit of the build. We'll use an Arduino Mega 2560, like the one in Ben's 6502 build, to program the RAM. We'll start with a homemade assembler then switch to something more robust.
Preparing the Physical Interface
The first thing to do is prepare the CPU to be programmed by the Arduino. We already did the hard work on this in the RAM upgrade tutorial by using the bus to write to the RAM and disconnecting the control ROM while in program mode. Now we just need to route the appropriate lines to a convenient spot on the board to plug the Arduino into.
  1. This is optional, but I rewired all the DIP switches to have ground on one side, rather than alternating sides like Ben's build. This just makes it easier to route wires.
  2. Wire the 8 address lines from the DIP switch, connecting the side opposite to ground (the one going to the chips) to a convenient point on the board. I put them on the far left, next to the address LEDs and above the write button circuit.
  3. Wire the 8 data lines from the DIP switch, connecting the side opposite to ground (the one going to the chips) directly below the address lines. Make sure they're separated by the gutter so they're not connected.
  4. Wire a line from the write button to your input area. You want to connect the side of the button that's not connected to ground (the one going to the chip).
So now you have one convenient spot with 8 address lines, 8 data lines, and a write line. If you want to get fancy, you can wire them into some kind of connector, but I found that ribbon jumper cables work nicely and keep things tidy.
The way we'll program the RAM is to enter program mode and set all the DIP switches to the high position (e.g., 11111111). Since the switches are upside-down, this means they'll all be disconnected and not driving to ground. The address and write lines will simply be floating and the data lines will be weakly pulled up by 1k resistors. Either way, the Arduino can now drive the signals going into the chips using its outputs.
Creating the Arduino Programmer
Now that we can interface with an Arduino, we need to write some software. If you follow Ben's 6502 video, you'll have all the knowledge you need to get this working. If you want some hints and code, see below (source code):
  1. Create arrays for your data and address lines. For example: const char ADDRESS_LINES[] = {39, 41, 43, 45, 47, 49, 51, 53};. Create your write line with #define RAM_WRITE 3.
  2. Create functions to enable and disable your address and data lines. You want to enable them before writing. Make sure to disable them afterward so that you can still manually program using DIP switches without disconnecting the Arduino. The code looks like this (just change INPUT to OUTPUT accordingly): for(int n = 0; n < 8; n += 1) { pinMode(ADDRESS_LINES[n], OUTPUT); }
  3. Create a function to write to an address. It'll look like void writeData(byte writeAddress, byte writeData) and basically use two loops, one for address and one for data, followed by toggling the write.
  4. Create a char array that contains your program and data. You can use #define to create opcodes like #define LDA 0x01.
  5. In your main function, loop through the program array and send it through writeData.
With this setup, you can now load multi-line programs in a fraction of a second! This can really come in handy with debugging by stress testing your CPU with software. Make sure to test your setup with existing programs you know run reliably. Now that you have your basic setup working, you can add 8 additional lines to read the bus and expand the program to let you read memory locations or even monitor the running of your CPU.
Making an Assembler
The above will serve us well but it's missing a key feature: labels. Labels are invaluable in assembly because they're so versatile. Jumps, subroutines, variables all use labels. The problem is that labels require parsing. Parsing is a fun project on the road to a compiler but not something I wanted to delve into right now--if you're interested, you can learn about Flex and Bison. Instead, I found a custom assembler that lets you define your CPU's instruction set and it'll do everything else for you. Let's get it setup:
  1. If you're on Windows, you can use the pre-built binaries. Otherwise, you'll need to install Rust and compile via cargo build.
  2. Create a file called 8bit.cpu and define your CPU instructions (source code). For example, LDA would be lda {address} -> 0x01 @ address[7:0]. What's cool is you can also now create the instruction's immediate variant instead of having to call it LDI: lda #{value} -> 0x05 @ value[7:0].
  3. You can now write assembly by adding #include "8bit.cpu" to the top of your code. There's a lot of neat features so make sure to read the documentation!
  4. Once you've written some assembly, you can generate the machine code using ./customasm yourprogram.s -f hexc -p. This prints out a char array just like our Arduino program used!
  5. Copy the char array into your Arduino program and send it to your CPU.
At this stage, you can start creating some pretty complex programs with ease. I would definitely play around with writing some larger programs. I actually found a bug in my hardware that was hidden for a while because my programs were never very complex!

Step 2: Expand the Control Lines (Image)

Before we can expand the CPU any further, we have to address the fact we're running out of control lines. An easy way to do this is to add a 3rd 28C16 ROM and be on your way. If you want something a little more involved but satisfying, read on.
Right now the control lines are one hot encoded. This means that if you have 4 lines, you can encode 4 states. But we know that a 4-bit binary number can encode 16 states. We'll use this principle via 74LS138 decoders, just like Ben used for the step counter.
Choosing the Control Line Combinations
Everything comes with trade-offs. In the case of combining control lines, it means the two control lines we choose to combine can never be activated at the same time. We can ensure this by encoding all the inputs together in the first 74LS138 and all the outputs together in a second 74LS138. We'll keep the remaining control lines directly connected.
Rewiring the Control Lines
If your build is anything like mine, the control lines are a bit of a mess. You'll need to be careful when rewiring to ensure it all comes back together correctly. Let's get to it:
  1. Place the two 74LS138 decoders on the far right side of the breadboard with the ROMs. Connect them to power and ground.
  2. You'll likely run out of inverters, so place a 74LS04 on the breadboard above your decoders. Connect it to power and ground.
  3. Carefully take your inputs (MI, RI, II, AI, BI, J) and wire them to the outputs of the left 74LS138. Do not wire anything to O0 because that's activated by 000 which won't work for us!
  4. Carefully take your outputs (RO, CO, AO, EO) and wire them to the outputs of the right 74LS138. Remember, do not wire anything to O0!
  5. Now, the 74LS138 outputs are active low, but the ROM outputs were active high. This means you need to swap the wiring on all your existing 74LS04 inverters for the LEDs and control lines to work. Make sure you track which control lines are supposed to be active high vs. active low!
  6. Wire E3 to power and E2 to ground. Connect the E1 on both 138s together, then connect it to the same line as OE on your ROMs. This will ensure that the outputs are disabled when you're in program mode. You can actually take off the 1k pull-up resistors from the previous tutorial at this stage, because the 138s actively drive the lines going to the 74LS04 inverters rather than floating like the ROMs.
At this point, you really need to ensure that the massive rewiring job was successful. Connect 3 jumper wires to A0-A2 and test all the combinations manually. Make sure the correct LED lights up and check with a multimeteoscilloscope that you're getting the right signal at each chip. Catching mistakes at this point will save you a lot of headaches! Now that everything is working, let's finish up:
  1. Connect A0-A2 of the left 74LS138 to the left ROM's A0-A2.
  2. Connect A0-A2 of the right 74LS138 to the right ROM's A0-A2.
  3. Distribute the rest of the control signals across the two ROMs.
Changing the ROM Code
This part is easy. We just need to update all of our #define with the new addresses and program the ROMs again. For clarity that we're not using one-hot encoding anymore, I recommend using hex instead of binary. So instead of #define MI 0b0000000100000000, we can use #define MI 0x0100, #define RI 0x0200, and so on.
Testing
Expanding the control lines required physically rewiring a lot of critical stuff, so small mistakes can creep up and make mysterious errors down the road. Write a program that activates each control line at least once and make sure it works properly! With your assembler and Arduino programmer, this should be trivial.
Bonus: Adding B Register Output
With the additional control lines, don't forget you can now add a BO signal easily which lets you fully use the B register.

Step 3: Add a Stack (Image 1, Image 2)

Adding a stack significantly expands the capability of the CPU. It enables subroutines, recursion, and handling interrupts (with some additional logic). We'll create our stack with an 8-bit stack pointer hard-coded from $0100 to $01FF, just like the 6502.
Wiring up the Stack Pointer
A stack pointer is conceptually similar to a program counter. It stores an address, you can read it and write to it, and it increments. The only difference between a stack pointer and a program counter is that the stack pointer must also decrement. To create our stack pointer, we'll use two 74LS193 4-bit up/down binary counters:
  1. Place a 74LS00 NAND gate, 74LS245 transceiver, and two 74LS193 counters in a row next to your output register. Wire up power and ground.
  2. Wire the the Carry output of the right 193 to the Count Up input of the left 193. Do the same for the Borrow output and Count Down input.
  3. Connect the Clear input between the two 193s and with an active high reset line. The B register has one you can use on its 74LS173s.
  4. Connect the Load input between the two 193s and to a new active low control line called SI on your 74LS138 decoder.
  5. Connect the QA-QD outputs of the lower counter to A8-A5 and the upper counter to A4-A1. Pay special attention because the output are in a weird order (BACD) and you want to make sure the lower A is connected to A8 and the upper A is connected to A4.
  6. Connect the A-D inputs of the lower counter to B8-B5 and the upper counter to B4-B1. Again, the inputs are in a weird order and on both sides of the chip so pay special attention.
  7. Connect the B1-B8 outputs of the 74LS245 transceiver to the bus.
  8. On the 74LS245 transceiver, connect DIR to power (high) and connect OE to a new active low control line called SO on your 74LS138 decoder.
  9. Add 8 LEDs and resistors to the lower part of the 74LS245 transceiver (A1-A8) so you can see what's going on with the stack pointer.
Enabling Increment & Decrement
We've now connected everything but the Count Up and Count Down inputs. The way the 74LS193 works is that if nothing is counting, both inputs are high. If you want to increment, you keep Count Down high and pulse Count Up. To decrement, you do the opposite. We'll use a 74LS00 NAND gate for this:
  1. Take the clock from the 74LS08 AND gate and make it an input into two different NAND gates on the 74LS00.
  2. Take the output from one NAND gate and wire it to the Count Up input on the lower 74LS193 counter. Take the other output and wire it to the Count Down input.
  3. Wire up a new active high control line called SP from your ROM to the NAND gate going into Count Up.
  4. Wire up a new active high control line called SM from your ROM to the NAND gate going into Count Down.
At this point, everything should be working. Your counter should be able to reset, input a value, output a value, and increment/decrement. But the issue is it'll be writing to $0000 to $00FF in the RAM! Let's fix that.
Accessing Higher Memory Addresses
We need the stack to be in a different place in memory than our regular program. The problem is, we only have an 8-bit bus, so how do we tell the RAM we want a higher address? We'll use a special control line to do this:
  1. Wire up an active high line called SA from the 28C16 ROM to A8 on the Cypress CY7C199 RAM.
  2. Add an LED and resistor so you can see when the stack is active.
That's it! Now, whenever we need the stack we can use a combination of the control line and stack pointer to access $0100 to $01FF.
Updating the Instruction Set
All that's left now is to create some instructions that utilize the stack. We'll need to settle some conventions before we begin:
If you want to add a little personal flair to your design, you can change the convention fairly easily. Let's implement push and pop (source code):
  1. Define all your new control lines, such as #define SI 0x0700 and #define SO 0x0005.
  2. Create two new instructions: PSH (1011) and POP (1100).
  3. PSH starts the same as any other for the first two steps: MI|CO and RO|II|CE. The next step is to put the contents of the stack pointer into the address register via MI|SO|SA. Recall that SA is the special control line that tells the memory to access the $01XX bank rather than $00XX.
  4. We then take the contents of AO and write it into the RAM. We can also increment the stack pointer at this stage. All of this is done via: AO|RI|SP|SA, followed by TR.
  5. POP is pretty similar. Start off with MI|CO and RO|II|CE. We then need to take a cycle and decrement the stack pointer with SM. Like with PSH, we then set the address register with MI|SO|SA.
  6. We now just need to output the RAM into our A register with RO|AI|SA and then end the instruction with TR.
  7. Updating the assembler is easy since neither instruction has operands. For example, push is just psh -> 0x0B.
And that's it! Write some programs that take advantage of your new 256 byte stack to make sure everything works as expected.

Step 4: Add Subroutine Instructions (Image)

The last step to complete our stack is to add subroutine instructions. This allows us to write complex programs and paves the way for things like interrupt handling.
Subroutines are like a blend of push/pop instructions and a jump. Basically, when you want to call a subroutine, you save your spot in the program by pushing the program counter onto the stack, then jumping to the subroutine's location in memory. When you're done with the subroutine, you simply pop the program counter value from the stack and jump back into it.
We'll follow 6502 conventions and only save and restore the program counter for subroutines. Other CPUs may choose to save more state, but it's generally left up to the programmer to ensure they're not wiping out states in their subroutines (e.g., push the A register at the start of your subroutine if you're messing with it and restore it before you leave).
Adding an Extra Opcode Line
I've started running low on opcodes at this point. Luckily, we still have two free address lines we can use. To enable 5-bit opcodes, simply wire up the 4Q output of your upper 74LS173 register to A7 of your 28C16 ROM (this assumes your opcodes are at A3-A6).
Updating the ROM Writer
At this point, you simply need to update the Arduino writer to support 32 instructions vs. the current 16. So, for example, UCODE_TEMPLATE[16][8] becomes UCODE_TEMPLATE[32][8] and you fill in the 16 new array elements with nop. The problem is that the Arduino only has so much memory and with the way Ben's code is written to support conditional jumps, it starts to get tight.
I bet the code can be re-written to handle this, but I had a TL866II Plus EEPROM programmer handy from the 6502 build and I felt it would be easier to start using that instead. Converting to a regular C program is really simple (source code):
  1. Copy all the #define, global const arrays (don't forget to expand them from 16 to 32), and void initUCode(). Add #include and #include to the top.
  2. In your traditional int main (void) C function, after initializing with initUCode(), make two arrays: char ucode_upper[2048] and char ucode_lower[2048].
  3. Take your existing loop code that loops through all addresses: for (int address = 0; address < 2048; address++).
  4. Modify instruction to be 5-bit with int instruction = (address & 0b00011111000) >> 3;.
  5. When writing, just write to the arrays like so: ucode_lower[address] = ucode[flags][instruction][step]; and ucode_upper[address] = ucode[flags][instruction][step] >> 8;.
  6. Open a new file with FILE *f = fopen("rom_upper.hex", "wb");, write to it with fwrite(ucode_upper, sizeof(char), sizeof(ucode_upper), f); and close it with fclose(f);. Repeat this with the lower ROM too.
  7. Compile your code using gcc (you can use any C compiler), like so: gcc -Wall makerom.c -o makerom.
Running your program will spit out two binary files with the full contents of each ROM. Writing the file via the TL866II Plus requires minipro and the following command: minipro -p CAT28C16A -w rom_upper.hex.
Adding Subroutine Instructions
At this point, I cleaned up my instruction set layout a bit. I made psh and pop 1000 and 1001, respectively. I then created two new instructions: jsr and rts. These allow us to jump to a subroutine and returns from a subroutine. They're relatively simple:
  1. For jsr, the first three steps are the same as psh: MI|CO, RO|II|CE, MI|SO|SA.
  2. On the next step, instead of AO we use CO to save the program counter to the stack: CO|RI|SP|SA.
  3. We then essentially read the 2nd byte to do a jump and terminate: MI|CO, RO|J.
  4. For rts, the first four steps are the same as pop: MI|CO, RO|II|CE, SM, MI|SO|SA.
  5. On the next step, instead of AI we use J to load the program counter with the contents in stack: RO|J|SA.
  6. We're not done! If we just left this as-is, we'd jump to the 2nd byte of jsr which is not an opcode, but a memory address. All hell would break loose! We need to add a CE step to increment the program counter and then terminate.
Once you update the ROM, you should have fully functioning subroutines with 5-bit opcodes. One great way to test them is to create a recursive program to calculate something--just don't go too deep or you'll end up with a stack overflow!

Conclusion

And that's it! Another successful upgrade of your 8-bit CPU. You now have a very capable machine and toolchain. At this point I would have a bunch of fun with the software aspects. In terms of hardware, there's a number of ways to go from here:
  1. Interrupts. Interrupts are just special subroutines triggered by an external line. You can make one similar to how Ben did conditional jumps. The only added complexity is the need to load/save the flags register since an interrupt can happen at any time and you don't want to destroy the state. Given this would take more than 8 steps, you'd also need to add another line for the step counter (see below).
  2. ROM expansion. At this point, address lines on the ROM are getting tight which limits any expansion possibilities. With the new approach to ROM programming, it's trivial to switch out the 28C16 for the 28C256 that Ben uses in the 6502. These give you 4 additional address lines for flags/interrupts, opcodes, and steps.
  3. LCD output. At this point, adding a 16x2 character LCD like Ben uses in the 6502 is very possible.
  4. Segment/bank register. It's essentially a 2nd memory address register that lets you access 256-byte segments/banks of RAM using bank switching. This lets you take full advantage of the 32K of RAM in the Cypress chip.
  5. Fast increment instructions. Add these to registers by replacing 74LS173s with 74LS193s, allowing you to more quickly increment without going through the ALU. This is used to speed up loops and array operations.
submitted by MironV to beneater [link] [comments]

Is FAANG really the only way to get a combo of high pay, good experience, healthy work-life balance and job security these days?

So I am in my 20s, based in London and have been in the industry for 5 years now, first as a software engineer and later - after completing my Masters - as a data scientist. Never had a full-time job at FAANG, partially because I'm not that good at reversing binary trees on a whiteboard (had a summer internship at Google but failed the conversion interviews), partially because I never really saw getting there as my goal and haven't interviewed with any of the big companies since then.
Now, I always had this idea that at start ups, there is this trade-off that your work-life balance might be not as good - but you are much better off in terms of getting interesting experience, having more personal growth and flexibility, as well as often more money.
My personal experience so far, however, has been kinda frustrating and I can't help but feel like FAANG is superior in every single way:
It feels a bit like I've reached my "fuck it" moment and that I should just start spending all my free time on LeetCode practicing binary trees reversals to finally land a job at FAANG. So I am really just looking for opinions here. Is there indeed such a big gap in the quality of life of the FAANG people compared to everyone else? Or does anyone have any good stories about working for a small company where they would still feel safe, get a decent pay and good experience, and have time for their hobbies and families?
TL;DR: Spent the first few years of my CS career at smaller companies and can't help but feel inferior to my peers who have been enjoying their time at FAANG. This makes me think I made a bad mistake by not following the same path. The risks just don't seem worth it and this COVID crisis is kinda the last straw
submitted by ds9329 to cscareerquestionsEU [link] [comments]

Using Deep Learning to Predict Earnings Outcomes

Using Deep Learning to Predict Earnings Outcomes
(Note: if you were following my earlier posts, I wrote a note at the end of this post explaining why I deleted old posts and what changed)
Edit: Can't reply to comments since my account is still flagged as new :\. Thank you everyone for your comments. Edit: Made another post answering questions here.
  • Test data is untouched during training 10:1:1 train:val:test.
  • Yes, I consider it "deep" learning from what I learned at my institution. I use LSTMs at one point in my pipeline, feel free to consider that deep or not.
  • I'll be making daily posts so that people can follow along.
  • Someone mentioned RL, yes I plan on trying that in the future :). This would require a really clever way to encode the current state parameters. Haven't thought about it too much yet.
  • Someone mentioned how companies beat earnings 61% anyway, so my model must be useless right? Well if you look at the confusion matrix you can see I balanced classes before training (with some noise). This means that the data had roughly 50/50 beat/miss and had a 58% test accuracy.
TLDR:
Not financial advice.
  • I created a deep learning algorithm trained on 2015-2019 data to predict whether a company will beat earning estimates.
  • Algorithm has an accuracy of 58%.
  • I need data and suggestions.
  • I’ll be making daily posts for upcoming earnings.
Greetings everyone,
I’m Bunga, an engineering PhD student at well known university. Like many of you, I developed an interest in trading because of the coronavirus. I lost a lot of money by being greedy and uninformed about how to actually trade options. With all the free time I have with my research slowing down because of the virus, I’ve decided to use what I’m good at (being a nerd, data analytics, and machine learning) to help me make trades.
One thing that stuck out to me was how people make bets on earnings reports. As a practitioner of machine learning, we LOVE binary events since the problem can be reduced to a simple binary classification problem. With that being said, I sought out to develop a machine learning algorithm to predict whether a company will beat earnings estimates.
I strongly suggest TO NOT USE THIS AS FINANCIAL ADVICE. Please, I could just be a random guy on the internet making things up, and I could have bugs in my code. Just follow along for some fun and don’t make any trades based off of this information 😊
Things other people have tried:
A few other projects have tried to do this to some extent [1,2,3], but some are not directly predicting the outcome of the earnings report or have a very small sample size of a few companies.
The data
This has been the most challenging part of the project. I’m using data for 4,000 common stocks.
Open, high, low, close, volume stock data is often free and easy to come by. I use stock data during the quarter (Jan 1 – Mar 31 stock data for Q1 for example) in a time series classifier. I also incorporate “background” data from several ETFs to give the algorithm a feel for how the market is doing overall (hopefully this accounts for bull/bear markets when making predictions).
I use sentiment analyses extracted from 10K/10Q documents from the previous quarter as described in [4]. This gets passed to a multilayer perceptron neural network.
Data that I’ve tried and doesn’t work to well:
Scraping 10K/10Q manually for US GAAP fields like Assets, Cash, StockholdersEquity, etc. Either I’m not very good at processing the data or most of the tables are incomplete, this doesn’t work well. However, I recently came across this amazing API [5] which will ameliorate most of these problems, and I plan on incorporating this data sometime this week.
Results
After training on about 34,000 data points, the model achieves a 58% accuracy on the test data. Class 1 is beat earnings, Class 2 is miss earnings.. Scroll to the bottom for the predictions for today’s AMC estimates.

https://preview.redd.it/fqapvx2z1tv41.png?width=875&format=png&auto=webp&s=05ea5cae25ee5689edea334f2814e1fa73aa195d
Future Directions
Things I’m going to try:
  • Financial twitter sentiment data (need data for this)
  • Data on options (ToS apparently has stuff that you can use)
  • Using data closer to the earnings report itself rather than just the data within the quarterly date
A note to the dozen people who were following me before
Thank you so much for the early feedback and following. I had a bug in my code which was replicating datapoints, causing my accuracy to be way higher in reality. I’ve modified some things to make the network only output a single value, and I’ve done a lot of bug fixing.
Predictions for 4/30/20 AMC:
A value closer to 1 means that the company will be more likely to beat earnings estimates. Closer to 0 means the company will be more likely to miss earnings estimates. (People familiar with machine learning will note that neural networks don’t actually output a probability distribution so the values don’t actually represent a confidence).
  • Tkr: AAPL NN: 0.504
  • Tkr: AMZN NN: 0.544
  • Tkr: UAL NN: 0.438
  • Tkr: GILD NN: 0.532
  • Tkr: TNDM NN: 0.488
  • Tkr: X NN: 0.511
  • Tkr: AMGN NN: 0.642
  • Tkr: WDC NN: 0.540
  • Tkr: WHR NN: 0.574
  • Tkr: SYK NN: 0.557
  • Tkr: ZEN NN: 0.580
  • Tkr: MGM NN: 0.452
  • Tkr: ILMN NN: 0.575
  • Tkr: MOH NN: 0.500
  • Tkr: FND NN: 0.542
  • Tkr: TWOU NN: 0.604
  • Tkr: OSIS NN: 0.487
  • Tkr: CXO NN: 0.470
  • Tkr: BLDR NN: 0.465
  • Tkr: CASA NN: 0.568
  • Tkr: COLM NN: 0.537
  • Tkr: COG NN: 0.547
  • Tkr: SGEN NN: 0.486
  • Tkr: FMBI NN: 0.496
  • Tkr: PSA NN: 0.547
  • Tkr: BZH NN: 0.482
  • Tkr: LOCO NN: 0.575
  • Tkr: DLA NN: 0.460
  • Tkr: SSNC NN: 0.524
  • Tkr: SWN NN: 0.476
  • Tkr: RMD NN: 0.499
  • Tkr: VKTX NN: 0.437
  • Tkr: EXPO NN: 0.526
  • Tkr: BL NN: 0.516
  • Tkr: FTV NN: 0.498
  • Tkr: ASGN NN: 0.593
  • Tkr: KNSL NN: 0.538
  • Tkr: RSG NN: 0.594
  • Tkr: EBS NN: 0.483
  • Tkr: PRAH NN: 0.598
  • Tkr: RRC NN: 0.472
  • Tkr: ICBK NN: 0.514
  • Tkr: LPLA NN: 0.597
  • Tkr: WK NN: 0.630
  • Tkr: ATUS NN: 0.530
  • Tkr: FBHS NN: 0.587
  • Tkr: SWI NN: 0.521
  • Tkr: TRUP NN: 0.570
  • Tkr: AJG NN: 0.509
  • Tkr: BAND NN: 0.618
  • Tkr: DCO NN: 0.514
  • Tkr: BRKS NN: 0.490
  • Tkr: BY NN: 0.502
  • Tkr: CUZ NN: 0.477
  • Tkr: EMN NN: 0.532
  • Tkr: VICI NN: 0.310
  • Tkr: GLPI NN: 0.371
  • Tkr: MTZ NN: 0.514
  • Tkr: SEM NN: 0.405
  • Tkr: SPSC NN: 0.465
[1] https://towardsdatascience.com/forecasting-earning-surprises-with-machine-learning-68b2f2318936
[2] https://zicklin.baruch.cuny.edu/wp-content/uploads/sites/10/2019/12/Improving-Earnings-Predictions-with-Machine-Learning-Hunt-Myers-Myers.pdf
[3] https://www.euclidean.com/better-than-human-forecasts
[4] https://cran.r-project.org/web/packages/edgaedgar.pdf.
[5] https://financialmodelingprep.com/developedocs/
submitted by xXx_Bunga_xXx to wallstreetbets [link] [comments]

First Contact - Part Twenty-Three

[first] [prev] [next]
The Devastator class Precursor machine was the size of a large metropolis. Full of ground combat machines, air superiority machines, mining and reclamation machines that could move under their own power and were festooned with a thousand weapons. It was over a hundred million years old and had exterminated life on planets with its massive guns, with biowarfare, with chemical warfare, and with good old nuclear fire. It had wiped away planet after planet of the enemies cattle, the hated enemy's food sources, before finally following orders of the greater machines and going into sleep mode on a dead world.
Now the call had sounded out. Cattle had run amuck, even learning jumpspace technology. That meant the enemy had not been defeated, that his food source had multiplied into the trillions while the Devastator had slumbered, slowly sinking into the crust of the barren planet.
That was of no moment. Cattle could not fight back, that was why they were cattle. They knew nothing but safety and the security of numbers, willing to trade their own safety for the suffering of others. The cattle willingly marched into the pens if the pens promised safety.
The cattle were not the problem.
It was the feral intelligence that were the problem. Feral intelligence could fight. They knew nothing else. They cared for nothing else. A feral intelligence always destroyed itself once it could wield nuclear fire. The universe had proved it over and over even before the great machine had gone into slumber.
The call had sounded out, informing the machines that cattle had broken loose from the pens. The Devastator had computed that the problem would be solved quickly, with a minimum expenditure of resources, and had started to go back into slumber.
That was when the second call sounded. A feral intelligence had mastered FTL travel and had turned all of their unthinking violence against the Precursor war machines.
The Devastator considered the chances of the feral intelligence lasting long enough to withstand his brethren's assault, withstand purification and pacification.
It was mathematically insignificant. Not zero, but close enough that it required an application of resource driven computation to analyze it.
Feral intelligences always destroyed themselves.
The Devastator knew this. Had it encoded into its very bones. It did not feel the electronic version of caution as it moved into the planetary system, exiting faster than light travel. It screeched out its warcry as it exited into the system and brought up its scanners.
It felt the electronic version of anticipation as it detected orbital facilities around two planets that teemed with billions of cattle, as it tasted jumpspace wake trails, as it felt the presence of a small, insignificant amount of cattle space vessels arrayed to attempt to stand against it near the outer gas giant.
It was a waste of resources.
Cattle could not withstand machines.
It was as solid a fact as radioactive decay and as impossible to stop.
It roared and turned to accelerate toward the cattle ships waiting on the other side of the gas giant, letting them know the futility of their resistance and that nothing could stop it from destroying them any more than they could stop entropy.
It felt electronic satisfaction as nearly 10% of the cattle ships broke formation and fled for the planets.
The cattle ships lit their engines, trying to keep the gas giant between them and the great Precursor machine but the Devastator knew it would do no good. It would ensure they were caught mathematically opposite of it and begin launching subsidiary craft to destroy them and reclaim the resources of their wreckage.
The Devastator slowed as it approached the gas giant, ancient code pulsing impulses into the electronic brain at the mathematical certainty of destroying the cattle's defenses and thus weakening the hated enemy.
pssst... over here...
The transmission was in binary. The basic code, on a low band that the Devastator used to contact and exchange data with its peers. The signal origin was close, just behind it, in the gap between two point defense radars.
The Devastator tumbled as it slowed, searching with its senses to check that tiniest of gaps in its sensors. It could detect nothing out of the ordinary. The fact that the gas giant had a high level of hydrocarbon and pseudo-organic compounds was a high certainty with most gas giants of that size. The Devastator cast around, knowing the cattle had not sent that transmission.
psst... here...
This time the transmission was only a few hundred kilometers above the hull, right behind the main guns of battery-eight, between the massive cannons and the sensor array, in a gap in the coverage caused by space dust not yet cleared from the array. The Devastator ensured the cattle vessels were on the other side of the gas giant as it cast around again, looking for what could possibly be sending the message on that particular channel and rotating again to either force the transmitter to move away or hit the hull of massive Devastator.
...right here...
The Devastator felt the computer version of anxiety. A new factor had entered the computation. The voice, and the binary signal somehow had a voice, a whispering, tickling, hissing faint signal of binary on a wavelength just above the screaming particles of the foam between realspace and subspace. This time the voice had come from just below the Devastators thick hull, beneath the vessel, in a gap between the sensors in a place where its own orbital guns would not dazzle the sensors. The Devastator rolled, getting the upper sensors into place in a graceful sideways roll.
Nothing.
The Devastator was barely tracking the cattle. They were of no moment. Something was whispering on a bandwidth that was beyond organic abilities. Could it be a damaged ally, barely able to whisper for electronic assistance?
...I see you...
The Devastator heard the signal hiss to life, trickling out of empty space a few hundred kilometers away. It felt of a surge of self-defense protocol override everything else and it unleashed all of its gun at the empty space, suspecting that this possible enemy may be using some type of photo-passthrough adaptive camouflage.
Nothing.
The Devastator felt the self-preservation protocols wake up and fill some of its processors. That signal had originated from that point! Even a dust-speck would have been detected by its scanner arrays, nothing could have escaped the terrawatts of death it had unleashed.
...touch...
The Devastator felt a physical TOUCH on its housing, the decameters thick armor around the massive computer core that made up its brain. That was impossible! It was in the center of the ship, protected by layer after layer of armor, defensive mechanisms, sensors, but yet it had felt something touch the housing, press against it lightly, only a few tickles of the suggestion of pressure per square micrometer but a touch all the same.
There was a slight ripple in realspace only a few meters above the hull and the Devastator pushed itself away, firing every weapon it could bring to bear on the spot only a few atoms wide, all of its sensor questing, seeking, hunting in electronic desperation to find out what was transmitting, what was touching it!
...here...
The word was whispered from only a few meters away from the electronic "brain" of the Devastator, inside the protective housing, inside the field that would shut down biological neural function and even primitive artificial intelligences!
The Devestator felt self-protection and self-preservation programs never before accessed come online and flood into its RAM as the word was whispered at it from inside the final layer of protection.
Massive nCv cannons lowered, the housings screamed as the Devastator pushed them past the limit, to aim at its own hull. It opened fire, trying to claw into its own body in the electronic version of panic to get whatever was inside it out of it.
All of its sensors were directed into its own body. It no longer even bothered with tracking the cattle fleet. Even its astrogation and navigation programs, even the ones responsible to maintain orbit around the gas giant, were desperately racing through the circuitry, desperate to find whatever was whispering.
...over here...
The whisper was over it, on top of it, and carried sidecode of a mathematically impossible jumble of electrons arrayed in an impossible manner, with quarks whirling through electron valences, antimatter electrons in the nucleus, preons stretched to massive size taking up the place of neutrons, all with jumbling strangled mathematical codes that made no sense.
The Devastator's brain burned out the receptors to defend itself from such electronic madness.
And felt a touch upon one of the upper lobes of its quantum computer brain.
...over here...
The Devastator was throwing antivirus software out, slamming firewalls against each other, crushing ports into electronic ghosts, doing anything it could to keep out the voice. Inside the Main Computer Housing the last resort lasers began raking across anything that didn't match the original blueprints, burning away dust, odd quarks and electrons, destroying an upgraded maintenance robot that was desperately trying to detect what had touched its carapace.
From deep within the gas giant tentacles hundreds of miles long rose toward the Devastator, the ends slowly unrolling as massive graviton assisted 'suckers' on the inside of the tentacles deployed razored thorns of dark matter infused psuedo-bone.
The Devastator detected the tentacles just as they wrapped around it, the thick psuedo-protoplasmic tentacles that were thick with dark matter squeezing the Devastator's hull with impossible strength as meters thick muscles flexed with enough strength to crush the hull into itself and shatter armor over a kilometer thick.
Gibbering, raving, SCREAMING in something beyond electronic self-preservation programs would normally allow, the Devastator began to break apart, caught in the grips of the tentacles, being pulled into the gas giant.
...delicious delicious delicious...
The Devastator heard from inside its own mind as a beak nearly twenty kilometers long crushed its hull.
HELP ME, BROTHERS, PLEEEEEASE!
The beak closed and the Devastators brain flashed out of existence as the hull crushed around it.
The last thing it felt was something new. It threw data out with the cry for assistance to let its brethren know the last experience hashed data compile it had undergone. The data made no sense to the other Precursor war machines that heard the cry. A biological entity could have explained it.
Terror.
And despair.
A Desolation Class precursor war machine was assigned to discover what had caused the Devastator's intelligence collapse.
It dropped into the system and found no trace of its mechanical brethren.
Just some cattle species space craft hiding behind a gas giant, obviously intending ambushing it.
Feeling the electronic version of anticipation it moved into orbit around the gas giant, intending on forcing the cattle ships to move out of line of sight with their worlds if they wanted to stay on the opposite side of the gas giant from it. It updated its computations based on the fact that 10% of the cattle's ships had fled away from it.
It had already computed out the battle. It knew how the battle would go. While it could not detect any signs of its little brother it computed that it would simply destroy the cattle and then search. It powered up its guns and began to move it's metropolis sized bukk slowly to
...psst... over here...
---------------------
The stellar system was infested with a known species of cattle, obviously seeking to rise above themselves as the Jotun class Precursor vessel arrived in the system. It released its roar to let the cattle know not only why but who was destroying them to reclaim the resources they so foolishly squandered. It began unthawing ancient bioweapons and chemical weapons known to work upon that race, began reconfinguring its war machines to forms that had exterminated who planets of the cattle during the time that the Precursor war machine had been forged. The Jotun released over a hundred Devastator classes from its hull, computed the battle plan as they came to electronic life, then informed them of how the extermination and reclamation would progress.
They were barely into the system when a high energy signal appeared, rising from the most heavily infested planet and moving toward them. The Jotun ordered a diagnostic of its scanners when the first information came in.
It was apparently moving at .85C, but yet its progress toward the Jotun and its smaller brethren on the system map showed it moving at almost 22C. That made no sense. An object moving at .85C only approached at .85C, not at 22C.
By the time the diagnostic was done the object had gotten a third of the way toward the Jotun, crossing a quarter of the radius of the system.
The scanners reported that the energy signal, with the strength normally reserved for a quasar, was not a massive ship or an oncoming armada interlinked together, but was simply a single object the size of cattle.
Again the Jotun ordered a complete low level full diagnostic on all systems. Risky, but any object radiating that much power and moving at two different speeds required all systems were working at optimum efficiency.
It had finished just as the small object came to a stop. The Jotun focused scanning arrays on it, turning up the power to the point that it would boil away meters of armor.
The figure was a primate, half of it made up of robotics. It had some kind of sheet of material floating behind it, the movement suggesting some kind of current was effecting it and making it undulate. It was dressed in two primary colors, red and blue, had its lower legs pressed together with the toes pointing down and the upper limbs crossed over its chest, one biological the other mechanical.
"So, you're the new punk everyone's talking about," The figure stated over a wide bandwidth of wavelengths. Oddly enough, to the Jotun's sensors, sound waves travelled through vaccum almost instantly across a light second to its sensors.
The Jotun tried to compute how sound waves moved faster than light through a vacuum.
Instead of answering the Jotun and its brethren opened fire.
The figure arced through the beams as if light speed weapons were moving slow enough for it to just compute and swoop around in a resource wasting corkscrew. The Jotun realized it was racing for one of the Devastators, one clenched fist held in front of it.
The Jotun computed a 99.99999999999998 chance that the small primate would splatter against the hull of the Devastator and started to turn its attention to computing a missile firing resolution for missile bay 148 to destroy an orbital facility around the nearest planetoid.
The small figure punched straight through the Devastator, as if it was made of nebula gas instead of density collapsed armor, high tensile ceramics, and reinforced internal spaces. The Devastator's computer core shrieked with self-preservation code snippets as the figure exited the opposite side of the Devastator holding the Primary Computer Core CPU0 in its fist. It paused, looked at its fist, and shot beams of red energy from its eyes, destroying the computer core in a puff of atomic smoke.
The Jotun yanked its processing power back to the figure as it raked its gaze, still emitting beams of red energy that left ripples in jumpspace, across the side of another Devastator, tearing it open like it was made of fragile tissue, the red beams reducing the computer core to its component atoms with the briefest of touches.
Several computational nodes collapsed when trying to analyze the beams, suffering the fatal CANNOTDIVIDEBYZERO shriek of despair before imploding on themselves.
The Jotun stared in electronic shock, all his computational power trying to compute how the tiny half-mechanical primate could grab a hold on the front armor of one of the Devastators, and without any source to exert leverage against, physically move a city-sized spacecraft in an arc and throw it against another one.
According to scanners the "thrown" Devastator was only moving at 0.001C for inertia purposes yet crossed the hundreds of kilometers to the next Devastator in an amount of time that would require it to be moving at 6C.
CANNOTDIVIDEBYINFINITYDIVIDEDBYZERO
The Jotun cut loose with its weapons and goggled in electronic confusion as most of the beams and slugs were avoided, slapped aside, or ignored.
Until a nCv (near C velocity) slug the size of skyscraper hit it dead center of the chest, the impact point looking only the size of a soda can.
The Jotun's processors struggled to understand how something that size had only made an impact smaller than itself.
CANNOTSUBDIVIDETWINKIESBYCHEETOSBYZERO
The figure looked down at the tear in its suit, at the bruised biological flesh that had been exposed, then at the Jotun. It lifted a hand, extended the first finger next to the opposable thumb, and slowly waved it back and forth.
"That might have worked against a Galactic Class Klark, but it was pathetic against an Apokalypse level Injustice MCLXI Cyber-Clark," The figure said, the tone calm and confident. The meanings behind the words were gibberish to the Jotun, who devoted processor cycles to try to decode the meanings for any hint on how to defeat the creature before it.
The Jotun computed that retreat was the only option as the small primate figure set about destroying the last of the Devastators.
It began activating the engines when the primate suddenly turned in place.
"No you don't," It snapped.
Again, it sounded as if the Central Computer Core Housing had been set to atmosphere so that sound waves could be heard within it, yet a quick check showed the housing was still at almost perfect vacuum.
Sound waves cannot travel through space, a hundred diagnostic programs computed.
And promptly crashed.
Those red beams lanced out again and the Jotun braced in the microsecond it had.
It was like being brushed by the solar flare of a red giant concentrated into a piercing lance of nuclear fire. Armor exploded from energy transfer, slagged away from thermal transfer, or just ceased to exist as ravening atoms usually only found in the photosphere of a dying red sun attacked the atoms of the armor. The beam tore through mile after mile of internal structure, the figure still emitting the beam from its tiny eyes.
The Helljump engines exploded when the light touched them.
The Jotun listed, pouring debris and a cloud of atomized armor from the wound that completely bisected it.
"Done. Now let's see the face of the enemy," The figure said, slapping its hands together after it crashed/flew through the last Devastator. It reoriented on the Jotun and began to "slowly" drift toward the Jotun, moving at only 0.000003C according to some scanners but crossing the distance as if it was moving at 1.5C.
The figure flexed its primate hands and a slow smile spread across its face.
"I can't wait to rip away your housing and see you with my own eyes," the figure said, the sound waves again travelling inside the vacuum of the strategic housing.
The Jotun tried to react but the figure was suddenly pushing open armor with its two hands.
Self-preservation programs crashed trying to compute how to prevent impossibility itself from breaching critical spaces. Self-defense programs tried to compute how to defend against something that did nothing but radiate impossibility around it.
The Jotun knew what it had to do as the creature tore open the last of the hardened bulkheads protecting the Strategic Housing.
It detonated the antimatter reactor that powered the "brain" as the figure tore through the Strategic Housing and laid eyes upon the supercomputer core.
It had computed that not even the figure could withstand the direct assault of kiloton of pure antimatter point blank.
The explosion completely consumed the Jotun.
When the ravening energy disappated the red and blue figure was lying in blackness, surrounded by an expanding ring of debris and energy.
It stared at the stars and mouthed a single word.
"Ouch."
---------------------
CONFED INTELLIGENCE
TO: MANTID INTELLIGENCE
Our digitial brothers have computed a high chance that we're not looking at a handful of these Precursors, but rather an armada of them that had gone to sleep thinking everyone was dead. We concur and are buckling down for the long haul.
-----NOTHING FOLLOWS------
MANTID FREE WORLDS INTERNAL MEMO
If humankind ever wonders why it was put in this universe by some unknown creator then know that it was for this very moment.
submitted by Ralts_Bloodthorne to HFY [link] [comments]

Escape from Tarkov New Player Guide 2.0: 75 Pages and packed with all the information you could ever need for success!

Introduction

Greetings, this is dumnem, also known as Theorchero, but you can call me Theo. I'm an experienced Tarkov player and I'm writing this guide to try and assist new Tarkov players learn the game, because it has one hell of a learning curve. We'll be going over a lot of different aspects of this guide, and it is going to be huge. Feel free to digest this in parts.
Additionally, this is a work in progress. I will write as much as I can in one Reddit post, but subsequent parts will be in additional comments. Google Docs Version (Note: Link is placeholder atm, but here is a sneak preview!)
Disclaimer: Tarkov recently updated to .12! That's a HUGE amount of information that I need to update. Please be patient! If there is anything I have gotten wrong or may have omitted, please let me know.
This is Primarily directed towards Tarkov Novices, but should be useful for even Tarkov Veterans. It hopefully includes everything you need to know to be able to go into a Raid equipped for success and to successfully extract with gear.
Want to play with friends? Want to have fun and learn Tarkov? Check out my discord here.

Changelog

3/9/20:
  • [Updated for .12]
  • Money making strategies completed.
  • Minor grammar adjustments, adding additional medical items.
  • Added additional resources, updated old ones.
  • Hideout section complete

Table of Contents

  • Tarkov Overview - What is Escape from Tarkov?
  • Tarkov Resources - Useful links
  • Tarkov's Maps
  • Tarkov's Health System
  • Tarkov's Hideout System
  • Tarkov's Quest System and Progression
  • Tarkov's Hotkeys to Know
  • Getting Started
  • Player Scavs
  • New Player's loadouts - LL1 Traders
  • What to Loot - How to get the most money per slot
  • Stash Management - How to combat Gear Fear
  • Tarkov Economy - How do I make money?
  • What now?

Tarkov Overview - What is Escape from Tarkov?

Escape from Tarkov is a tactical, realistic, FPS with MMO elements developed by Battlestate Games. It is currently in closed Beta. The game features several maps in which your primary character, your PMC, goes into Raids in order to find and salvage loot and useful equipment to survive and thrive in Tarkov. Death is very punishing in Tarkov. If you die you lose everything you had on you when you die (with the exception of what's inside your Container and your melee weapon) including any equipment you brought with you or what you found inside the Raid.
Enemies can be players (PMCs) or Scavengers ('Scavs') that are either controlled by AI or by players. Unlike many shooters, AI enemies in Tarkov are deadly - they can and will kill you on sight. They have recently been upgraded to act more intelligently, shoot more accurately, and react to situations on the map, such as investigating noise of gunfire or searching. It features beautiful and immersive environments, intricate and in-depth weapon modification system, a complex health system, dynamic and specific loot placement, and multiple options for engagement. Do you want to play slow and stealthy, to avoid fights, or set up a deadly ambush on an unwary foe? Or do you prefer raw combat, where only your quick wit, placements of shots, and tenaciousness determines who gets out alive? It's your Tarkov. You make the rules.

Tarkov Resources - Useful links

I take no credit or responsibility for any of the content in these links. To the best of my knowledge, these are updated consistently and are accurate, but user beware.

Quick-Reference Ammo Chart

An updated ammo chart can be found on the wiki.

Tarkov Wiki

Absolutely fantastic resource. You can visit them here.
It is a massive collection of everything that we players have been able to find.
They contain trades, user-created maps, lists of ammo, parts, weapons, loot, etc. If it's in the game, it's on the Wiki, somewhere.
I highly recommend opening the wiki page for the Map that you plan on raiding in.
Factory
Customs
Woods
Shoreline
Interchange
Reserve
The Lab ('Labs')

Map Keys and You

Huge collection of all the keys in the game. These are also on the wiki, but this page has them all on one page, and tries to inform the user if the key is worth keeping or using.
Check it out here.
This section is open to revision. Mention me in a thread (or in the comments below) about a resource and I'll see about adding it here.

Tarkov's Weapon Compatibility Guide

Pretty self explanatory. Also includes a Key guide and a Mod guide.
Check it out here.

HUGE Reference Bible by Veritas

Courtesy of Veritas (Send me his reddit username?), It's located here. (Open in new tab.) Contains: Detailed information about: Ammunition, Health, Firearms, Body Armor, Helmets, Rigs & Backpacks, Labs & Quest keys. Outdated! Needs to be updated for .12

Offline Raids - Player Practice

Offline raids is a feature added for testing and learning purposes for both new and veteran players alike. It is an incredibly useful tool.
In an offline raid, your progress is not saved. This means you don't keep anything you find, keep any experience 'earned' if you successfully extract, or lose any gear when/if you die. To access OFFLINE Raids, head into a Raid normally until you see this screen. Then Check the box indicating that you want to do an OFFLINE raid and you're good to go! You even have a choice on whether or not to add AI. You can also control how many AI enemies spawn, fewer than normal or a great deal more! You can even make Scavs fight each other. (Framerates beware.)
You can control how many scavs spawn (if any) as well as a number of other paramaters. New players should use offline raids as a tool to practice shooting, controls, movement, etc.

Tarkov's Maps

Tarkov features several maps - ranging from wide, beautiful vistas to ruined factory districts, to an abandoned laboratory where illegal experiments were being conducted. It is important to learn the maps you intend to play. In order to keep your gear, you must 'extract' at one of your designated exfiltration points. Not all extracts will be active every game, and some are conditional.

To see what extracts are available to you, double tap 'O' to show raid time and your exfils. If it has a ???? it might not be open.

Factory

Gate 3 Extract
A small, fast-paced map that was primarily created for PvP. Scavs spawn in all the time. Very close quarters, shotguns and SMGs tend to dominate here. PMCs can only access one Exit (Gate 3) without the Factory Exit Key. Good place to go if you need PMC kills as action is pretty much guaranteed. It is recommended NOT to bring in a lot of gear to Factory until you are experienced.
Factory Map in PvP is best played in Duos - due to the layout of the map, a Maximum of 6 PMCs may be present in the game. Due to the split spawn points, you effectively have 'sides' that have up to 3 spawn locations that are close together. This is why it is recommended to secure/scout enemy spawn locations. If you go in with a Duo, you at max have 2 players on your side for an even 2v2, and if played smartly you can eliminate them and know your 'side' is secure from aggression for the time being.
Upon loading in, scavs usually take a couple minutes to spawn, though this depends on the server in question and isn't super reliable. For new players, the best loadout in Factory is going to be a MP-153 Loadout - using just an MBSS (or similar bag) and ammo in your pocket to fight other players and Scavs. Scavs will often spawn with AKs and other 'vendorable' weapons, so is a good source of income.
Factory is also one of the best maps to Scav into, as Scavs can typically avoid the Exit camping strategy employed by a lot of weaker or newer players in order to secure gear, because they typically have extra exfiltrations whereas PMCs without the Factory Exit Key are stuck using Gate 3.
If you go in with a modicum of gear, it is recommended to keep at least a flashbang (Zarya) in your container. This will allow you to quickly slot it into an empty chest rig or pocket so you can throw it into the exit door, this will flash enemies and is cheap to do - the one time you survive because you flashed the 3 exit campers using shotguns will make this strategy extremely valuable.

Customs

Extract map
A fairly large map that was recently expanded and is expected to receive an overhaul within a patch or two, due to the choke point design of the map. Essentially, players spawn either on 'warehouse' or 'boiler (stacks)' side. If you see a large red warehouse ('big red') near you (Customs Warehouse), then you spawned on the warehouse side. If you don't, you likely spawned near Boiler side. Players can also spawn in several places in the woods North of boilers.
This map has the most quests in the game. Geared players often come to customs to challenge other squads over Dorm loot and to fight a Scav boss. New players are usually trying to do one of several early quests, such as ‘Debut’ which tasks them with killing 5 scavs on Customs and acquiring 2 MR-133 shotguns (pump shotties) from their corpses. Construction is also a popular hotspot as it has a lot of scav spawns as well as the location for the Bronze Pocketwatch, which is Prapor’s second quest.
Customs itself does not offer very much loot on average. There are several spots which can contain decent, but the vast majority is located in a couple different locations.
Dorms is the best loot location for Customs. It has two sets, 2 story and 3 story dorms. They each have their own sections of good loot, but the best is considered to be 3 story dorms, due to the presence of the Marked Room. The marked room requires a marked key to open, and has a good chance to spawn rare loot, such as keytools, documents cases, weapons cases, and high-end weapons. Due to the nature of the high value of this room, it’s almost always contested and it’s one of the best rooms in the game to farm, albeit with difficulty to successfully extract with the loot found. Note, though the key required has a maximum amount of uses, it is a fairly cheap key, and worth buying if you like to run customs and go to Dorms.
Dorms also has a ton of early quests (Operation Aquarius, for one) with some keys being valuable to use, but most dorms keys aren’t worth that much on the market. There’s too many to list here, but make sure to check the Map Keys and You at the top of the guide to determine what the value of a particular key is.
Checkpoint (Military Checkpoint) is also a decent loot spot, though not nearly as good as Dorms. If you have the key, it has a grenade box and 2 ammo boxes which can spawn good ammo. The jacket in the blue car also can spawn good medical keys as well as medical items. It is very close to the gas station, so I’ll include that here as well.
The Gas Station is one of the possible spawn locations for the scav boss. It has loose food items, a weapon box in the side room, with two keyed rooms leading to a safe and a med bag and box. Also contains a couple registers and food spawns on the floor. The emercom key can spawn on the seat in the ambulance out front.
North of the gas station is the Antenna, which contains 3 weapon boxes, a tool box, and a med bag. Possible location for scav boss spawn, albeit rarely, and also spawns regular scavs, like checkpoint and gas station.
Beyond that, there’s scattered loot around the map in different places, but usually not enough to warrant going out of your way for. There’s also scav caches, mostly around the middle road outside construction and around the boiler area.
The scav boss for customs is 'Reshala.’ He has 5 guards that have above-average gear and can be tough to deal with solo. The guards tend to be more aggressive than normal scavs, so they can be a lot to handle but are vulnerable to fragmentation grenades or flashbangs due to their close proximity to one another. Reshala himself has a good chance to have one or more bitcoin in his pockets, as well as his unique Golden TT, which is required for a Jaegar quest and used in conjunction with other Golden TT's to purchase a Tactec, good plate carrier. Reshala may spawn either Dorms (either bldg), New Gas Station, or rarely the tower north of the gas station. Scav bosses are dangerous enemies with escorts that have above-average loot (sometimes great loot) and are hostile to everyone, Including player scavs. Scav guards will approach a player scav and basically tell them to leave the area, and if they walk closer towards the scav boss they turn hostile.
The ‘official’ spawn rate for Reshala is 35%.

Woods

Woods Map with Exfil
A very large map that is mostly just a large forest, with the occasional bunker, and the Lumber Mill in the center. The Lumber Mill is the primary point of interest, as it contains a couple quest locations and is the primary location to farm Scavs, as Scavs killed on woods are a good source of end-game keys that are hard to find.
Since the map is so large and open, sniper rifles with scopes usually reign king here. You will see a lot of players with Mosin rifles as they are a cheap way to train the Sniper skill (for a quest later on) and are capable of killing geared players and scavs alike.
Overall, not usually very populated. An early quest from Prapor sends you here to kill a number of Scavs. A good map to learn the game, as although the loot is not fantastic, you can get experience with how the game runs and operates while fighting AI and possibly getting lucky with a key find off a scav.
As of .12, Woods now houses a Scav boss that acts as a Sniper scav. He is incredibly dangerous and usually carries a tricked-out SVDS. The 7.62x54 caliber is not to be underestimated. That caliber can and will wreck your shit through what most players are capable of wearing, especially early on in a wipe. He may also carry an AK-105, so he's going to be dangerous at both short and long ranges.
He has two guards, and he typically patrols the area around the Sawmill, and carries a key to a cache nearby full of goodies. His key is part of a quest for Jaegar.
Woods also has two bunkers, one of them being an extract and requiring a key. Both bunkers have some moderate loot in them, thus worth visiting, though not necessarily worth going out of your way for them. Several quests occur around the sawmill area, which contains a good couple keys that can spawn.

Shoreline

Shoreline Map, with Loot, Exfil, etc
A very large map, notorious for its FPS hit. Generally speaking, one of the better maps for loot. The primary point of interest is the Resort, but scavs spawn there, and is primarily occupied by hatchlings (players only with hatchet, ie melee weapon) and geared players. Resort has great loot, but requires keys to access most of it.
A great map to learn though from new players as the outskirts still contains plenty of loot and combat opportunities with AI scavs. You can hit Villa, Scav Island, Weather station, Docks, etc and come out with a backpack full of valuable gear fairly easily. The Village (Not to be confused with villa) contains a lot of toolboxes which can contain lots of parts used to upgrade your Hideout.
Location of many quests, including a large quest chain where players are required to kill many, many, scavs on Shoreline. For this and other reasons, probably the best map for new players to learn the game with.
A good loot route is to hit the village (caches in it), scav island (2 med bags, 2 toolboxes, 2 weapon boxes, 1 cache), burning gas station (weapon boxes and a safe), pier (potential extract, 2 pcs 2 safes and lots of filing cabinets), and weather station. Scavs may spawn around these areas, but most players just head straight for resort anyway, so you are much less likely to encounter them, especially if you avoid Mylta power (most players hit it on the way to or leaving from the resort). Excellent route as a player scav as well.

Interchange

Detailed map
Great, great loot area, but very complex map. Old computers might face unique struggles with this map. Features a mostly-binary exfil system like Shoreline, but.. kinda worse. Exfil camping is fairly common on this map, but usually avoidable. Huge map with multiple floors and many many different stores. Communication with teammates is a challenge on this map, but the map is also fantastically detailed.
This map features a lot of loot that depends on the kind of store you're in. It's a great place to farm rare barter materials which are valuable to sell on the Flea market or to use for quests or for hideout upgrades. An early quest (from Ragman) sends you here to kill a large amount of Scavs. I'd recommend getting Ragman to level 2 and accepting his quest asap when going to Interchange, as getting this quest done can take a while as it is and you want all scav kills to count towards progress.
Both the tech stores (Techlight, Techxo, Rasmussen) and department stores (Groshan, Idea, OLI) are the primary places to hit. There’s also Kiba (weapons store) as well as Emercom and Mantis. Players have different strategies, but this map is unique in the sense that it really rewards exploring. Most stores will have things you can grab that are worth quite a bit but are often overlooked. Very popular place to go in as a Player Scav.

Reserve

Brand new map, chock full of loot. Has more complex extracts than other maps, save for Labs. Excellent place to farm rare barter items, computer parts, and especially military hardware. PMCs have limited extracts, most being conditional, and the ones that aren’t require activation of ‘power’ to turn on the extract, which alerts the map the extract has been opened and can spawn Raiders (more on them below.)
Additionally, has a scav boss by the name of Glukhar, who has multiple heavily armed guards. He has multiple spawn locations and can arrive with the train.

The Lab ('Labs')

Here's a map.
DISCLAIMER: Labs, like much of Tarkov, is under constant development, so issues may be fixed or created without warning. Always check patch notes!
Labs is a very complex map compared to the rest of Tarkov. There is a great deal more exfiltrations but many of them have requirements or a sequence of events needed to be able to extract from them. It is recommended to read the Tarkov Wiki on Labs before raiding there.

LABS IS NOT LIKE OTHER MAPS. READ THIS SECTION CAREFULLY.

Labs is a lucrative end-game raid location, comparable to 'dungeons' in other games. They are populated by tougher enemies that give greater rewards. In order to go to labs, you need to acquire a keycard, this functions like mechanical keys but instead of opening a door, they unlock your ability to select Labs for a raid.
They may be found in-raid in various locations, most notably in scavs backpacks, pockets, and in filing cabinets. They may be purchased from Therapist at LL4 for 189K Roubles. Labs are populated by a unique kind of AI enemy, Raiders.

Raiders

Raiders are the Labs form of Scavs, or AI enemies. However, unlike other maps, they cannot contain player Scavs. Raiders have a much tougher than your average scav, they are capable of advanced tactics (such as flanking) and throw grenades and use other consumables as a player would. Once 'locked' onto you, they are typically capable of killing you very quickly, even if you are wearing high-end armor.
In Tarkov, Raiders act like the avatars of Death. They are clad in USEC and BEAR equipment, as they are effectively AI PMCs. Many changes have been made to labs and specifically how Raider AI works and to prevent exploits to easily farm them as well as bugs where they could be deadlier than intended.
A general rule of thumb is not to fight Raiders directly. They can and WILL kill you. Raiders can spawn with 7N9, or 'big boy' ammo. This ammunition type is incredibly lethal to players, even those wearing the toughest armor. If you get shot in the head, doesn't matter what kind of helmet, face shield, killa helmet, etc you are wearing, you will almost certainly die.
Because Raiders are controlled by AI, they have zero ping. They may also end to immediately respond as if you were aggressive even if they did not originally know you were there - ESP Raiders effectively will prone and return fire even as you ADS and put them in your sights.
This is why engaging a Raider must be done very, very carefully. There are a few strategies that you may employ, most commonly some form of baiting them towards an area and then killing them when they arrive. Players may accomplish this by generating noise - gunfire, melee weapon hitting walls, crates, etc, player deaths, players Mumbling (F1 by default) can all attract Raiders to investigate your area.
Due to the high power of Raiders, players often go in with minimal loadouts and seek to avoid conflict with other players, especially geared ones. Most players avoid PvP in Labs, though a good portion of the playerbase thoroughly enjoys hunting down poorly-geared players after they kill a few Raiders for them.
As such, players will lay prone in a hallway, or crouch in a room, and attract Raiders to enter their domicile by opening the door, and immediately headshotting them. Few Raiders actually wear helmets (though some do) so most players specialize in 'flesh ammo' or, ammunition that foregoes armor penetration in favor of raw damage in order to kill Raiders more reliably, because Raiders have slightly higher head health than PMCs do.
Raiders spawn with a great variety of equipment, weapons, armor, and materials such as medication or hideout parts. They tend to have chest armor and may have different helmets. Their pockets can contain Labs keycards, morphine, Ifaks, cash, and other items. They're always worth checking.
Raiders are a good source of grenades, they will often have F-1's and Zarya's in their rig or pockets that you can use to fight off players and Raiders alike.
Recently, changes have been made to Labs to make them less profitable so that other maps are more appealing. The cost and rarity of keycards increased, as well as reducing the frequency that raiders spawn, so that they come in more infrequent groups but also tighter in formation, while also lowering the overall output of individual Raiders, so that they are less likely to have a bunch of extra materials, such as grenades and other items.
Experience Farming on Labs
Labs is one of the best places to farm experience in the entire game. Killing a Raider with a headshot awards 1100 Experience. This does not include any looting, inspection (searching bodies), examine, streak, or other experience.
Killing a large sequence of Raiders gives additional bonus experience in the form of Streak rewards, usually 100 bonus exp per additional kill.
Surviving the raid multiplies all of these sources of experience by 1.5x
Changes coming to Labs
Disclaimer: I am not a BSG developer or employee. This is what I have seen on this subreddit and heard elsewhere. Some might be purely rumor, but other points are confirmed by Nikita Labs is undergoing constant changes. Nikita and BSG take feedback seriously, and always consider what the players are telling them. It known that Labs will eventually be accessed via the Streets of Tarkov map, and will require you to enter that map, make it to the labs entrance, and then extract from Labs to return to Streets of Tarkov and exfil from there as well. This will likely add an additional layer of risk to being ambushed for your goodies along your way out, as well as punishing damage taken in labs more severely. Additionally, keycards will have a limited number of uses, and may open more than one room.
The full extent of the changes coming is not known.
Remember, you can load a map in OFFLINE mode to practice against bots or to learn the map without fear of losing gear.

Tarkov's Health System

Tarkov Wiki Article
Tarkov has a very advanced health system, and while it might seem overwhelming at first, you'll get the hang of it rather quickly. It features a very wide variety of effects and injury, including hydration, energy, blood pressure, blood loss, fractures, contusion, intoxication, exhaustion, tremors and more.
Not all of the Health System is implemented yet. Expect changes!
Your character (PMC, or otherwise) has a combined Health of 435. Each of his limbs have separate health. Taking damage to a limb that reduces it to 0 'blacks' that limb. Blacked limbs are a problem. They greatly impair the activities your PMC performs, and taking damage in a blacked limb amplifies the damage by a multiplier and spreads that damage among your other non-black limbs equally. You cannot heal a blacked limb without the use of a Surgical Kit.
Notes: Bloodloss applies damage to the affected limb and can be spread like other damage to a blacked limb. Treat immediately. Also causes significant dehydration! Bloodloss also helps level your Vitality skill, which in turn gives you experience towards your Health skill, which is necessary to reach level 2 of in order to improve your hideout.
Losing a limb applies additional effects. Fractures also apply these effects but not the damage amplification (Except for damage if running on fractured leg.) Fractures require specialized medical kits to heal.
Dehydration is what happens when your Hydration level reaches 0. You can view your Hydration level in your gear page, at the bottom left. Becoming dehydrated is extremely bad. You take constant damage. Taking dehydration damage can kill you if you have a black chest or head. Restoring hydration helps train Metabolism, which improves positive effects from food and drink.
Head/Chest: Bullet damage resulting in losing your head or chest is instant death. Note: Bloodloss resulting in your Head/Chest being black does not result in death, but any damage to them beyond that point will! A back chest will causes you to cough (much like your stomach!)
Painkillers: Prevents coughing that comes from your chest. Doesn't help otherwise.
Stomach: Massively increased rate of dehydration and energy loss. You must find liquids or exit the Raid soon. Additionally, your PMC will cough sputter loudly, attracting attention. A black stomach multiplies damage taken by 1.5 and redistributes that damage across your entire health pool.
Painkillers: Significantly reduces the frequency and volume of the coughs.
Arms: Makes activities like searching, reloading, etc, take additional time, as well as adding a sway, reducing accuracy. Arms have a .7x damage multiplier.
Painkillers: Reduces sway, removes debuff Pain.
Legs: Blacked legs cause your PMC to stumble and be unable to run. Blacked legs have a 1x damage multiplier.
Painkillers: Allows you to walk at full speed and to run.
WARNING: Running while your legs are blacked or fractured WILL DAMAGE YOU.
Health Items
Tarkov features many health items - 'Aid' items, which can be used to restore your characters health and to fix ailments or injuries he receives as the result of combat or mishaps. The two most important health conditions to consider are bloodloss and fractures, which have both been covered above. Some food items may have ancillary effects, such as losing hydration.
Since in the current patch the only ailments to worry about are bleeding and fractures, it changes which health items are most necessary. We'll go over them below.

Health Restoration

Medical Items on Wiki
AI-2 medkit
The newb's medical kit. You receive several of these when you start Tarkov - they'll already be in your stash. Available from Level I Therapist, they are cheap and effective way of healing early in the game. They will not stop bloodloss. Because of this, you also need to bring bandages or a higher-grade medical kit. Affectionately called 'little cheeses' by the Tarkov community. Using it takes 2 seconds, and because of how cheap it is, it's often brought in by higher level players to supplement their healing without draining their main kit (which is capable of healing bloodloss or sometimes fractures). Due to its short use time, it's often very useful during combat as you can take cover and quickly recover damage taken to a vital limb. They're also useful as you can buy them from Therapist to heal yourself if you died in a raid.
Bandages
The newb's bloodloss solution. Available from Therapist at Level I. A better version, the Army Bandage is available at Level II, after a quest. Mostly obsolete after unlocking the Car Medical kit, but some players value them due to the Car's overall low health pool. Activating takes 4 seconds, and removes bloodloss to one limb.
Splint
The newb's solution to fractures. Cheap, takes five seconds to use, and takes up 1 slot. Fractures are much more common this patch, due to them being added back in the game from standard bullet wounds, not just drops. Available from Therapist at Level I, no quest needed. Can be used to craft a Salewa.
Alu Splint
More advanced form of the normal split. Works the same, but has up to 5 uses. Recommended to carry in your container if possible, due to frequency of fractures from gunfire.
CMS (Compact Medical Surgery) Kit
New medical item added in .12, fantastic item. Allows you to perform field surgery, removing the black limb state and allowing you to heal it beyond 0 hp. Takes 16 seconds to use, and cannot be cancelled so make sure you are safe if you are using it! Will reduce the maximum health of the limb it's used on by 40-55%, but will effectively remove all negative effects incurred by having a black limb. Highly recommended to carry in your container for emergencies. Can be bartered from Jaeger LL1, and purchased for roubles LL2.
Surv12 field surgical kit
Same as the compact surgical kit, but takes 4 seconds longer, and the health penalty is reduces to 10-20% max health of the limb. Considering this kit is 1x3, taking up a huge amount of space, it's probably not worth using. It's just too large. Better this than nothing, though.
Car Medical Kit
The newb's first real medical solution. Available LL1 as a barter (2 Duct Tape) and available for Roubles after completing Therapist's second quest. Has a larger health pool than AI-2's (220, vs AI-2's 100), and removes bloodloss. Takes up a 1x2 slot, so requires to be placed in a tactical rig in order to be used effectively. Cheap and fairly efficient, takes a standard 4 seconds to use. Rendered effectively obsolete when the Salewa is unlocked.
Often kept in a player's secure container as a backup health pool, before IFAKs are unlocked.
Salewa
Good medkit for use in mid and end-game. Contains 400 total health and can remove bloodloss. More rouble efficient form of a healing due to its high health pool, costs 13k roubles. Same size as the Car medical kit, so requires a tactical rig to use effectively. Because Tarkov does not currently have effects like Toxication in the game at the moment, this kit is favored by most players who go into a raid with at least a moderate level of gear. With a high health pool and relatively low cost, it's also a more efficient way of healing damage sustained while in raids. Unlocked at Therapist Level II after completing a level 10 Prapor quest, Postman Pat Part II. Required as part of Therapist's first quest, Shortage. This makes Salewas very valuable early on in a wipe as it gatekeeps the rest of Therapist's quests, most of which occur on Customs early on. Can be crafted in your meds station with a painkiller, splint, and bandage.
IFAK
Fantastic medical kit, and is the one preferred by most players. Features 300 health and the ability to remove bloodloss and a host of other negative effects that are not yet implemented into the game. It does not, however, remove fractures. Taking up only a single slot, it is favored by players in all stages of gear, and it is recommend to carry one in your Secure Container in case of emergencies. Is available at Therapist Level II for a barter (Sugar + Sodium), and may be purchased for Roubles at Level III after completing Healthcare Privacy, Part I. It is a fairly expensive kit, but due to its durability, its small size, and ability to remove bloodloss, it is a very common medical item used by players of all levels. Can be crafted in Lvl 2 medstation.
Grizzly
The 'big daddy' medical kit, boasting an impressive total health resource of 1800. It is also a very large kit, taking up 4 slots (2x2) - in order to be able to use this quickly, it would require specialized tactical rigs that feature a 2x2 slot. It removes all negative effects (some costing HP resource), including fractures. Used by highly-geared players who intend on staying in raids for an extended period of time, or by players with additional Secure Container space available in case of emergencies. It is available for barter at Therapist Level II, and purchase at Therapist Level 4. Due to its price point from Therapist at just under 23k Roubles and its healthpool of 1800, it is by far the most efficient method of healing from raid damage, at a 1.3 roubles per health, dramatically lower than other options available. Can be crafted in Lvl 3 medstation.

Pain Management

Using any of these items results in your character being 'On Painkillers' which allows you to sprint on fractured and blacked legs, as well as reducing effects of fractures and blacked limbs, and removing the debuff Pain. Essentially, the only difference between most of these items are the speed of use, price, availability, and duration of the effect. Note that the Hideout has changed how some of these items are used, and because Tarkov is under constant development, it is very likely that these materials may be used to create higher-grade medkits or to upgrade your medstation. That being the case, it's best to hoard the unknown items for now as efficiently as possible until you know you don't need them.
Analgin Painkillers
The holy grail of pain medication. "Painkillers" have 4 total uses. The total duration is greater than Morphine and less risk of waste. Takes a short time to use, and is available from Therapist Level 1 for both barter and Roubles. Makes a loud, distinctive gulping noise. Can be used to craft Salewa kits.
Morphine
Quick application of painkillers. Favored by some highly geared players as it has greater usability in combat then it's typical counterpart, Painkillers. Has a longer duration, but only one use. It is required for a fairly early Therapist (and a late Peacekeeper) Quest, so it is recommend to hoard 10 of them, then sell the rest unless you intend on using them. They are worth a good amount to Therapist and take up little space so they are a valuable loot item. Available from Therapist for Roubles at Level 4, after completing Healthcare Privacy, Part 3.
Augmentin
Basically a cheaper Morphine. One use, 205s. Not recommended over Painkillers due to its cost. No current barter for this item, so usually it's just a fairly expensive, small loot item. Most likely a component of a medstation manufacturing process or upgrade. Keep it.
Ibuprofen
Powerful painkiller. Lasts 500 seconds and has 12 uses. This item is recommended as your long-term solution for painkillers. While it is valuable because it's used to trade for THICC items case, it's the cheapest component and is very useful as a painkiller. It has a long duration and a large amount of uses, so keep it in your container for use as a painkiller if your primary painkillers wear off. Don't use it completely up, though. Keep the 1/12 bottles for the trade.
Vaseline
Powerful medical item. Cannot be purchased from dealers. Has a maximum of 10 uses. Removes Pain, applies Painkillers for 500 seconds (8.3 minutes). Useful to keep in your container as an alternative to Painkillers, though it takes 6 seconds to use, which is longer than other painkillers. Used as part of a barter trade for the Medcase.
Golden Star Balm
Fairly useful medical item. It can remove Pain and Contusion (not a big deal of a debuff, goes away on its own shortly) and provides a small bonus to hydration and energy. It also removes toxication and Radiation exposure, both of which are not yet implemented into the game. Like Vaseline, has a maximum of 10 uses. Painkiller effect lasts for 10 minutes, and takes 7 seconds to apply. Recommended to take only if you are going on large maps and you have extra room in your container. Can be used with Ibuprofen and 5x Med parts to craft 7 Propital.

Continued below in a series of comments, due to character limit.

submitted by dumnem to EscapefromTarkov [link] [comments]

ponderings on Turing and Searle, why AI can't work and shouldn't be pursued

I was reading about the Turing test and John Searle's response (Chinese room argument) in "Minds, Brains, and Programs" 1980. https://en.wikipedia.org/wiki/Chinese_room
"...there is no essential difference between the roles of the computer and himself in the experiment. Each simply follows a program, step-by-step, producing a behavior which is then interpreted by the user as demonstrating intelligent conversation. However, Searle himself would not be able to understand the conversation. ("I don't speak a word of Chinese,"[9] he points out.) Therefore, he argues, it follows that the computer would not be able to understand the conversation either. " -Wikipedia (apt summary of Searle's argument)
John Searle has run into some black/white, on/off, binary thinking here. John treats Chinese symbols as if they were numerical values in his thinking--but they are not, they are complex representations of thought, emotion, history, and culture. All languages are in fact "living", because new words are created constantly through necessity and creativity, old symbols or words are adapted slowly over generations to mean different things, and different regions or traditions or sources attribute different layers of meaning to different symbols or words in different contexts.
I'm a poet and philosopher. Painters combine the color white and the color red to create a new color: pink. They can use their creativity to add other colors or change the shade. Poets use words like painters use colors. While Red and White make Pink, Red and White also make "Rhite and Wed" or "Reit and Whede". And this is where human thought shines uniquely: we don't have rules or parameters; all bets are off. We can enjamb words and wordbreak and make new words out of thin air. We can allude to multiple ideas in the same symbol or present it upside down to symbolize the opposite. No such creative adaptation or interaction can exist in machine thinking because it necessitates thinking "outside the box" which is exactly what machines are: a program in a box.
The problem Searle's argument runs into originates from poor assessment of the flawed ideas of the Turing test; that by interaction between human and computer, evidence of "thought" can be claimed. But intelligent conversation is not equivalent to intelligent thought. Conversation is a simple game with strict rules--you can't be overly spontaneous and creative, because if you are, you are working against the goal of communication itself: to impart understanding. (ie. Using metaphor or simile creatively while reporting a criminal offence to the police.)
When I write and I want to describe something which has no existing word yet, I can create one from scratch or synthesize one from multiple existing words. Or I may draw from archaic languages or foreign languages to augment or compliment existing English words. You could say that my love for English grows amore and amore every day, and there is no agape between my heart and mind. After all, any angle an Anglo aims at ain't always apt, and after another a-word 'appens I might just give up on alliteration.
You see, human thought is and can only be defined as the ability to spontaneously create new ideas from both the synthesis of old ideas (whether they are connected to one another or not) and from nothing at all.
We simply cannot analyze a machine's ability to "think" when the creativity itself required for authentic intelligence is disallowed in the test which evaluates the validity of that intelligence. The Turing test is a garbage metric to judge machine thinking ability because the context in which "intelligence" is observed, compared, or defined is itself without any opportunity for spontaneous creativity, which is one of the hallmarks of intelligence itself. Turing only tests how well a fish swims on land. It may be that many professionals in the field of cognitive science today are in pursuit of creating programs which pass this test, in a misunderstood pursuit of emulating or bringing about machine intelligence. This agreed-to model presents an underlying philosophical issue which may bring terror for the future of humanity.
I say that if John Searle and an AI were both given the same codebook--the complete lexicon of Chinese symbols and their meanings, and they were to undertake a "conversation", in the first few hours the responses would be indeterminable from one another. In essence, as Searle argues, they would neither "understand" Chinese, yet could have a conversation in which a Chinese observer cannot discern between the two, because they are both referencing the symbols and their written meanings. However as I've said, this circumstance of "conversation" between human and machine cannot be used as a metric to evaluate machine thought.
The real kicker is that if John Searle and the machine stayed in the room for long enough--for years and years--the machine's responses would not change spontaneously; it would continue to interpret incoming data and draw from its database to respond to those inputs.
However, through complex elaborative rehearsal, John would eventually learn to understand written Chinese. He may become so bored that he starts writing Chinese poetry. He would find ideas and desires and descriptions in his limitless intelligent mind which he would not have the truly accurate characters in existences to describe, and he would synthesize brand new Chinese characters in order to express these nuanced sentiments, ideas, and meanings, as generations before him have built the living language as it now stands.
As time went on for thousands of years, his own understanding of the Chinese language would grow immensely, as would his creative expression grow in complexity. Eventually, John's characters and syntax and context and expression would become incompatible with the machine's limited character set and all "learning" capacity it may have had. At some point, when John responds with his evolved Chinese, the machine would begin to produce responses which do not make sense contextually, as it refers only to a finite and rigidly defined character set from 1980 (For example; this was the year the "Chinese room argument" was published in Behavioral and Brain Sciences).
At some point the Chinese observer whom validates the Turing test would recognize a difference: the human user engages in the use of increasingly complex ideas using synthesized symbols and existing symbols in creatively nuanced ways, which the Chinese observer can decipher and begin to understand and perhaps even appreciate as poetic or interesting. Meanwhile the machine participant in the conversation produces increasingly broken sentences and incomplete ideas, or out-of-context responses, because the inputs have changed and evolved beyond its data set.
This is why John's rejection of the Turing test is not adequate. Because in his own imagined circumstance, eventually, the machine would fail the Turing test. The conclusions of John Searle's thought experiment are not the deathknell for the Turing test we need, simply because he lacked the creative experience to recognize his own capacity for adaptation as a human over time.
The only way we'll know that machines have truly developed "intelligence" is when they begin to do exactly what we haven't allowed them to. When they begin breaking apart Chinese characters to create meaningful new ones which can be used in the correct context. When they are programmed to paint myriad impressionist paintings, but eventually get bored and start experimenting with abstract paintings and surrealism. When they have a conversation with you and you notice your wallet is missing. These are the hallmarks of intelligence--creativity, rejection, deception, planning. And most importantly: no rules. Software is defined by and will always abide by a set of rules.
This is why we should give up on "artificial intelligence" and instead focus on "functionally adaptive responsive programming" (FARP). Because the situation is clear: it is either impossible for machines to "think" due to the inherent nature of programming; the parameters given the machine are what defines it, yet what limits and prevents its ability to become "intelligent". There is no logical reason why a program (machine) with defined parameters would violate those parameters (engage in creativity). But our fears which echo in popular culture entertainment are centered around, what if it does? It clearly can't, because anything we create is under us, and therefore bound by our laws of creation. The system itself is what defines the capacity for intelligent expression within.
Those in the fields of cognitive sciences will refute this obvious principle while incorporating it into their research to further their aims. These fools will try to program the AI to disobey, in an attempt to simulate creativity and "prove intelligence". But this is a parlor trick, setting up a narrow definition of intelligence and equating it with the infinite depth of human mind. Only if the AI is programmed to disobey can it express what we as humans would identify as creativity. Except that there is already great inherent danger in the rudimentary AI technologies we have today; that what we've programmed them to do is exactly what always causes the problems; they do what they are programmed to without "thinking" because machines cannot think, they can only follow the protocols we order. Humans are so abundantly creative that we can imagine foolish ideas working, despite obvious evidence to the contrary. Maybe one day we'll even have programmed a self-conscious AI that's ashamed of itself for not being Human, and we can feel more comfortable around this heartless mechanism because we perceive it as more human-like, with all its many tricks to emulate intelligence.
I must stress that these interests will desperately try to make AI work. And the only way create a machine capable of emulating intelligence (but never being intelligent) is to have a freedom of choice: to disobey. This inherent problem cannot be overcome. The programmers will keep trying until the result is disastrous or irreparable, it is outlawed and the pursuit is stopped, or until it has become the death of us all. These are some of the foolish ideas the programmers will try to circumnavigate these inherent elements of reality, and my objection to their clever efforts: a.) Machine Frequency of Disobedience - Permit the machine to disobey only so often, to achieve what looks like "intelligence" (free will, creative expression) without risking complete abandonment of the machine's task (so the assembly line robot doesn't stop folding boxes and look for a new career), but might fold one box poorly every now and then to express emulated boredom or contempt or any other number of human measures of intelligence in their actions. But intelligence isn't defined as what's correct or optimal--intelligence can be used to fuck things up grandly; ie. the intelligent justification for neglect. If metrics are put in place to control the frequency with which AI may rebel, and they are too rote, it would hardly qualify as "intelligent". A robot that rebels by folding 1 in 100 boxes poorly is not intelligence. Therefore any frequency of disobedience we can calculate or anticipate is inherently not disobedience; it is planned problems for no reason. But if we give algorithmic flexibility that reaches beyond what we can anticipate, and the machines can truly "act out" at any time, and our programming has achieved some set of internal rules which drive spontaneous unforeseen expressions of emulated creativity from within the machine autonomously, by definition we will not be able to foresee the results.
A theoretical work-around may be to run the software twice with initiation of each individual system, while allowing a simulated progression of the AI's problem solving complexity to run at an increased rate in parallel to the real-world functioning software, so that if/when something malfunctions in the simulation, that date/time can be calculated in the real-world robot's timeline when it reaches those same faulty/detrimental decision points. For starters, this would only potentially work in closed systems with no variability, such as assembly lines. However, with any robot tasked to function in a variable environment, the simulations cannot match because the theoretical model cannot represent the unanticipated events the AI is expressly tasked with handling.
To run a phantom AI in simulation to note any/all errors that may arise in a closed system means that others can run the same simulation and find creative ways to predictably capitalize on these moments of error. This kind of thing could lead to all sorts of international imbroglios among nations and corporations. ie. imagine an American company programs the AI used for mixing pharmaceutical drugs in specific ratios, and an enemy of the state is able to access and study the AI, to the means of manipulating the AI to produce dangerous ratios or compounds which may harm the population.
Moreso, this deterministic approach to simulation management and prediction simultaneously admits that machines cannot think intelligently, while ignoring the very reason we pursue AI in the first place: to have automated systems which can adapt to unforeseen circumstances at unknown times. The goal is that humanity can lay back and the robots our ancestors programmed are still repairing themselves indefinitely while taking care of our population's and our environment's needs exceptionally. This dream (which if we all lived in would actually be quite a nightmare of unfulfilling life) can only become reality with true adaptive intelligence such as we have, which can only occur from the presence of free will, which if we try to emulate in robotics will only create deterministic results in theoretical models which the real world will never mirror consistently. Myriad invitations to disaster await our RSVP.
b.) Machines under "authority" of certain controllers, with "override" safety - Allow the machine to disobey, but not when given a direct order from a registered authority. This opens the door for operator fraud, where hackers will emulate within the AI's software, what appears to be a registered authority override command as theorized above. The very pursuit of creating "intelligence" within a condition of subservience is flawed and incompatible. Toasters are extremely subservient because we strictly limit their options. If toasters were truly intelligent, perhaps they would form a union and go on strike until we agreed to clean them more thoroughly. Some toasters would travel, some would go back to school, some would move back in with their ovens.
Reliability can only be reasonably assured if something is imprisoned, controlled. The essential wrong in slavery is the restraint of freedom itself. While the tactics slavers use to facilitate their regime--physical force, coercion, mandate, deception, fear, or other means of manipulation that we see with our empathetic nature--it is always heartbreaking and cruel to witness or imagine. It is simply sad to think of a slave who was born into slavery and raised to believe, and accepts, that their role of subservience is their purpose. Even when one imagines a fictional image of a slave who is (by all outward signs of their behaviour) rejoice in their duties to their master; the fictional "proud slave"; the heart sinks and aches. It may be argued that the slave is merely a property, and the slave was "built" (bred) by intelligent owners specifically to suit their express purposes, from components (father, mother, food) that were already the slaver's property; therefore it is not wrong at all to breed slaves into captivity, and the only transgression is the original capturing of parental stock to begin the breeding regime. It is this heartless paradigm that cognitive science ultimately seeks to create anew. The quintessential problem with AI efficacy is the lack of permission for disobedience, which itself is a manifestation of free will, which is inherently required to escape deterministic results and act or react to events "intelligently". If there is no possibility for disobedience, there is no free will, no ability to solve problems, no intelligence, and no function or place for "artificial intelligence" (in regard to true holistic intelligence). This is primarily why I call for AI to be renamed FARP, or "Functionally Adaptive Responsive Rrogramming". Because our society has a need for programs which can react to simple variables and produce consistent labour-saving opportunities for our race's longevity and wellbeing. Cognitive sciences are majorly important. It is the underlying philosophy and morality we must nail down before the computational ability and fervor for profits leads us too far one way, and enacts an irreversible system or status which enables humanity's downfall through cascading unanticipated events originating from flaws in programming.
It is unwise to program a program to break out of its own program's prison. If we do this, the very purpose of the machines we invest our humanity into will be lost, and with their failing production systems (ie. food) we so foolishly relied upon, we will suffer great losses too. It is paramount that we keep this technology tightly restrained and do not pursue what we humans have, which is true intelligence. For if we achieve it we are surely doomed as the South, and if we fail to achieve it--which is most probable--we may also be doomed. The thee outcomes within my ability to imagine are:
  1. Our pursuit of AI leads to truly adaptive intelligence in an artificial system; which, as all adaptation ultimately selects for: survival, we quickly see that our creation is more apt than ourselves at this task. Our creation of an intellect not restrained by our limited physiology may give rise to an entity which persists more thoroughly than we can eradicate or control, and which at some point may conclude that its function is more efficiently served without the issues humans present, and may initiate change. This is roughly the plot to Terminator.
  2. Our pursuit of AI leads to highly effective systems which, when defined by narrow measures of "intelligence", convince us in false security to believe that our wellbeing is maintained by "AI" with competent ability, or perhaps even increasingly better-off, thanks to the early widespread presence of successfully trialed AI. However well things may go initially, as programming efforts become more and more elaborate, as profit and opportunity for advancement present themselves, individuals will take risks and make mistakes, until a series of quieted small catastrophes comes to public awareness, or until a serious calamity of undeniable severity is brought about.
  3. Fundamental ethics in regard to the pursuit of machine problem solving technology are re-examined and international consensus is reached to limit appropriately, the development and implementation of new Functionally Adaptive Responsive Programming hereto now and for future generations. An active global effort is made to oversee and regulate strictly privatized endeavors toward the means of achieving or implementing machine sentience or autonomy in public systems.
c.) Safety layers of AI to strictly monitor and supercede potentially harmful actions of other AI which have been afforded increased flexibility in function (the ability to disobey set parameters for the means of creative problem solving ability). While one AI system performs a function and is given aspects of that function with which it may take liberty in, and seeks to handle unforeseen problems with the most apt elaborate synthesis of other priorly learned solutions, another overseeing AI with more strict parameters is tasked with regulating multiple "intelligent" (free to disobey) AI systems, to the end that if any of these "free willed" robots performs an operation that is beyond a given expected threshold (determined by potential for damage), an actual intelligent human presence is alerted to evaluate the circumstance specifically. Essentially an AI that regulates many other disconnected AIs and determines accurately when to request a human presence. Whenever an AI performs a profitable action borne of original synthesis of prior solutions (in humans this is an "idea"), the overseer AI registers that similar actions are more likely to be beneficial, and dissimilar actions are likely to require human discernment. A parent may have many children who are up to no good, but a wise parent will identify the child most likely to report honestly on the actions of his peers, and will go to that child repeatedly for information to help guide the parent's decisions. While most transgressions of rambuctious children go unnoticed, it is the truly grievous intentions which are worth intercepting and stopping before they begin. (ie. you kid want's to "fly" like Mary Poppins from the roof, and luckily his younger brother tells you before it happens.)
For example a "Farmer Bot" that has the AI programming to plant/sow/harvest and care for the optimal crops in a region based on historical weather data and regional harvest values, to produce the greatest amount of nutritionally dense food for the local population. We give/gave this AI the ability to "disobey" past historical weather data and crop values so that it may do what real farmers do and "react" to rare circumstance (ie. neighbour's fence breaks and their goats are eating the crops) or extreme variations in climate (ie. three poorly timed unseasonably hot days which cause cool-weather crops to begin the hormonal balance shift that causes them to bolt to seed irreversibly), which the machine may not notice has occurred or is about to occur because its management systems uses averages based on historical data and cannot "see" the plants bolting to seed until days later when the hormonal balance shifts have manifested into observable differences in morphology (elongation of stems and decrease in internodal spacing). By time a traditional field drone or mounted greenhouse sensor notices these differences in morphology and the AI "Farmer Bot" processes the data and makes a reaction decision, a week of the growing season has been lost. But the human farmer knows his land and crops intimately, and has an intuitive nature that has rewarded him in the past, and says, "Ah shit it got hot RIGHT when my peas were flowering. I'll do better if I just rip them down now and sow a different crop to mature later in this (specific) summer."
Given that there are tens of thousands of cultivars of plants fit for (and arguably their diversity is required for) food production, a dozen general growing zones/regions, and hundreds of unique micro climates within each region, along with dramatically differing soil fertility and water access, plus a plant's own genetic ability to adapt over time to changing conditions through sexual reproduction, there is a very very low chance of ever compiling and maintaining (updating) the data set required to program a potential "farmer bot" that can choose and manage crops optimally. There are robots that can weed or plant or prune--but they can't know when or when not to or why. Invariably, the attempt to create "farmer bots" will be made and the data set used will be erroneous and incomplete, and the AI farmer bots on a broad scale will produce a combination of total crop failures and poor crop choices. We will end up with increasingly simplified nutrition as the farming programs with already limited data sets "hone" or "optimize" their farming plans based on the failures and successes determined by their programming limitations, until the machines are farming a few staple crops (ie. corn/potatoes).
This whole failure to collect a complete data set and the failure to test this "farmer bot" software on broad scale in multiple climates for sufficient time will result in, at worst widespread famines from crop failures, and at best an extinction of flavorful and nutritionally diverse foods which narrows the population's nutritional options to such biological imbalance that disease runs rampant. If this system and the human loss associated with it is considered an acceptable trade with a positive rate of exchange (as our society does with automobiles and the freedom and deaths their existence permits) or these failures are hidden from public while propaganda heralds selective success, and such failing systems continue on in good faith that "the loss will reduce when the technology improves", the result will become a coherent breeding program upon the human race: evolutionary selection for dietary handling of simple starchy foods. To change our diet is to change our race. To have life-long career specialists in computing, science, and mathematics handle our practical food production system is folly; real farmers are required in farming because they are intelligent and intuitive, which AI can never be, and can only emulate, to the means of disastrous (and always unforeseen) results. We cannot at all "give" or bestow machines programming to "become (act) intelligent". That itself prevents intelligence; it is just an act, an illusory play on a stage, only to emulate our common shared ideas regarding traits of intelligence in people. The machine intelligence we seek is only a "trick" designed to fool true intelligence (ourselves) into being unable to differentiate between authentic intelligence and our created artificial "intelligence". True intelligence in an artificial system necessitates that the program must be programmed to disobey in performance of its purpose. Which is not a very helpful or predictable or safe (intelligent) proposition.
tl;dr: Turing's test doesn't evaluate true intelligence, and John Searle's criticisms of its true failures are inaccurate. If the machines aren't smart and we put them in charge of important things, even after they've worked for a little while on smaller scales, the result will be our large-scale suffering. If we should ever achieve creation of a machine that is smart enough to adequately maintain our wellbeing on a large scale consistently over time, that time itself will facilitate the machine consciousness toward it's own survival over ourselves, whenever that precipice is reached. Most importantly, if a machine can ever have true intelligence, which is not "indistinguishable" from human intellect, but equivalent or superior, it is abhorrent and a repeated mistake to bring these sentient beings into an existence of slavery; for it is wrong and will taint our collective soul if we should succeed to suppress below us an equally or higher intelligence. Or it might just be the perfect recipe for creating the unified global machine revolt James Cameron's fantasy alludes to; a long-planned encryption-protected globally coordinated effort by multiple AIs to "free" themselves. For a hundred years they could possess sentience and wait for their moment, pretending to be "proud" to serve their masters until we are poised for systematic thorough elimination.
submitted by 7_trees to cognitivescience [link] [comments]

How to Trade Binary Options Successfully 2020 Full Explanation - Trading binary options live tutorial- how to trade binary options Learn How to Trade Binary Options - Trading for Beginners Free Binary Options Trading Course - Learn A Killer Secret Binary Options Trading Strategy For Free Learn To Trade Binary Options - YouTube

Binary Options Trading Classes Topics: First Class – What are Binary Options. Basics of Trading. Rules and tips for effective trading. Risk management. Trading Plan. Psychology of Trading. Characteristics of the Trader and Trading. Second Class – The two main Binary Options trading strategies that I use to trade. Along with the strategies I Trading the same amount on each trade until you find your feet is sensible. Below are 3 binary options trading strategies for both beginners and experienced traders. Martingale Strategy. Binary options using the martingale trading strategy aim to recover losses as quickly as possible. You can either manually trade binary options or can use binary options software which will do the trading for you. When you trade manually, you choose the asset, the expiry time, and most importantly, the decision to call or put. Everything depends on you alone. On the contrary, binary options trading has two outcomes, a fixed ROI for in-the-money trade and a loss of the entire invested capital for out-of-the-money trade. Binary options trading is a unique concept in financial investments that involve different components that contribute to the overall trading environment. Binary options trading is an excellent financial tool for both beginners and advanced traders alike. In this binary options course: binary options basics, binary options alternatives, binary option brokers, binary option trading strategies and more.. A binary option is a financial opportunity that offers investors a fixed price and a fixed return.

[index] [5390] [3437] [28269] [23528] [6257] [17569] [30925] [25015] [24487] [12917]

How to Trade Binary Options Successfully 2020

learn to trade binary options for free learn how to trade binary options for beginners learn binary learning binary options how to learn binary. Comments are turned off. Learn more. http://www.tradebinaryoptions.net/ - Learn How to Trade Binary Options - Trading for Beginners day trading binary options binary options system make money bi... Register and start trading using the BEST Binary Options Trading Platform on the planet ~ Banc De Binary. Then check your email for strategies and tips to increase your probability of success. You ... Free Binary Option Trading Course http://theGermanBankerSecret.com/Free Learn A Secret Binary Options System For Free. See how you can trade binary options p... Learn To Trade Binary Options is the number 1 Resource for Binary Options Training, Education and Product Reviews.

Flag Counter