Item number SCP-2935 Object Class, Keter Special Containment Procedures The entrance of SCP-2935 has been sealed with concrete, and access to SCP-2935 is forbidden. Description SCP-2935 was a space-time anomaly existing within a limestone cave beneath a cemetery near Japa, Indiana. The cemetery, whose last entered individual died in 1908, was discovered by Foundation personnel after radio signals were discovered emanating from SCP-2935. See Addendum 2935.1 below. The SCP-2935 anomaly is a nearly exact replicate reality of modern Earth in the year 2016, with the primary exception being that all life, including both biological and non-biological, as well as any sentient entities, machines, computers, and other life-like phenomena within SCP-2935 ended on April 20, 2016. Information gathered by the Mobile Task Force, who initially entered SCP-2935 for reconnaissance purposes, points to the conclusion that all life forms within SCP-2935, suddenly and without warning, expired sometime between the hours of 0300-0400 EST. Addendum 2935.1 Discovery On April 28, 2016, at roughly 0500 EST, a radio signal was detected by communications personnel at Site-81 near Bloomington, Indiana. This signal, although distorted and unintelligible, was traced to the unincorporated area of Japa, Indiana near US Interstate 70. Site-81 personnel at Indianapolis were dispatched to determine the source of the signal as per Foundation policy, and discovered SCP-2935 during their examination of the area. Upon initial entry into SCP-2935, the aforementioned personnel were uncertain that they had actually discovered an anomaly, instead believing their drone had exited the other side of the cave. This was quickly corrected during observation of the surrounding area, and upon picking up the undistorted radio broadcast they had been searching for. The broadcast, which appeared to have been repeating on a loop since April 20, was an automated message originating from Site-81 within the SCP-2935 reality. The full transcription of the message is as follows. This is an automated emergency broadcast from the SCP Foundation and your national government. One or more of our sites is experiencing a communication breakdown, likely due to a containment breach of unknown magnitude. All citizens are ordered to stay in their homes as containment teams work to secure the breach. This message will broadcast from April 20, 2016 until… Message cuts out suddenly and then repeats. Afterwards, the Site-81 personnel contacted Site Command. Mobile Task Force Epsilon-13 manifests destiny, with immediately assigned to examination of exploration of SCP-2935. Addendum 2935.2 Exploration of SCP-2935 by MTF Epsilon-13 took place over four separate missions, three manned and one unmanned. During these missions, several artifacts and pieces of information will be covered, and a full list with descriptions available in Addendum 2935.3 Exploratory Mission 2935.1 Codename, Gauntlet Mission Abstract To survey and collect information and samples from the area directly surrounding the SCP-2935 insertion point Assigned Task Force Mobile Task Force Epsilon-13 manifests destiny, four members. Additional Information The following is a transcript of audio and video recordings captured by MTF E13 who were tasked with surveying SCP-2935 immediately after its discovery. The four manned team, led by Agent Juno, spent just over one hour during the preliminary assessment of the anomaly. Begin Log Mic's on Check Check Check Command We hear you. Confirm that all agents are at the insertion point. Confirmed. Alright. Proceed with insertion. Don't take any chances in there. We have no idea where you're going to see. Understood. Moving in. The MTF E13 team enters SCP-2935. Travel through the cave system takes roughly 15 minutes, after which the team emerges on the opposite side of SCP-2935. After cameras adjust to sunlight, the surrounding landscape is visible. Christ.  Confirm what we're seeing here, lead? Yeah, uh, looks like a total lack of living vegetation. Trees, grasses, everything looks dead. Water readings coming in at 24 degrees Celsius. Sound right? Affirmative. It's pretty pleasant. Cloudy, but not a lot of wind. Understood. Go ahead and proceed. Team, look for any housing. Is this the area we just left? We're trying to confirm that. Can you identify anything nearby? If we go up this ridge, there should be a road there, the one we came in on. Let's head that way. Team moves up nearby ridge. Yep, that's the road. Command. We're not certain yet, but preliminary observation points to this being the same locality as our side of the cave. Understood. Perceive a caution. Understood. Team moves north of the nearby road. After roughly two kilometers of travel, team encounters a farmhouse. Two cars sit outside. Command, there's a house over here. Gonna go check it out. Understood. Team, lead. Have underwoods set up the broadcast relay you've got. We want to try to respond to that signal. Got that command. I'll set it up now. Alright, let's move in. Team moves to the front door of the farmhouse. The door is unlocked. Front parlor is vacant, and Agent Kale confirms that power still works within the structure. Agents move for the kitchen. Jesus Christ, what- Three adult corpses, two female and one male, are seated at a table within the kitchen. The fourth corpse, a male child, lays nearby. Command, you can see this? We can. Can you confirm life signs in any of those individuals? I can.  This had to be pretty recent. No signs of decomp.  There is a newspaper on the table. April 19, 2016, Hendricks County Flyer. Command, can you confirm the headline? One moment, team. Dinner, look. Chicken, mashed potatoes, green beans. Confirming that headline, it's accurate with that newspaper on that date.  It's stale, but there's no- Wal-Clock says the date is April 28, 2016. That's today. Same time, too. April 9, 2015, same as my time. How long have they been here? Boss, look. The food. What about it? It's covered in dust. They- they are, too. They've been here for a while, but the food, it's all stale, but it's not rotten. That chicken should have been covered in mold by now. But there's nothing, see? Even the potatoes. Yeah, I see it. Team, we want to get some samples. Some of that food. Samples from the individuals in the room. Air, skin, fluids, if you can get them. Any electronics in the room? There's a laptop on a desk in the next room. A smartphone in that woman's pocket. Let me- yeah, battery's dead. Collect it. See if there's anything else to note nearby, and get back outside. We don't want to keep you over there for too long until we know more about that environment. Agent Kale collects biological samples from the corpses, as well as from the food on the table. Agent Juno surveys the rest of the home. Agent Devon moves to the living room and turns on television. The TV works, just flipping around, there's not a whole lot other than test signals.  What do you got? I think it's the Home Shopping Network, look. Television shows the set of the Home Shopping Network. Two individuals are on screen, one laying near an empty chair and the other facing the camera directly. Neither individual is moving. Backdrop has been burned. The fire suppression system seems to have been triggered, and red emergency lights flash on screen. Marquis at the bottom of the screen scrolls as usual. Date reads April 28, 2016. Alright, yeah, let's get out of here. Kale, come on, we're moving. Team leaves the house in rendezvous with Agent Underwood, who is finishing setting up the broadcast relay. After an additional 15 minutes, MTF-E13 returns to SCP-2935 insertion point. Before returning, Agent Kale collects samples of nearby vegetation for study. You know what I just realized, boss? What's that? It's summer in the Midwest. Do you feel like anything is missing? What do you mean? Listen, there's nothing. No birds, no insects, no car noise, nothing. Just the wind. It's so goddamn quiet. End log. Note, at the conclusion of this mission, team return to the SCP-2935 access point. However, team was then given instructions to stay within SCP-2935 and establish a forward camp and await additional members of MTF-E13. Exploratory mission 2935.2, codename Overland. Mission abstract, to gain access to a Foundation site, Site-81, in attempt to retrieve information from the Foundation server therein, and establish a forward camp there. Assigned Task Force, Mobile Task Force Epsilon-13, Manifest Destiny, 16 members. Additional Information. The following is a transcript to audio and video recordings captured by MTF-E13. The 16-man recovery team, laid by agents Juno and Roy, were given instructions to commandeer functional vehicles within SCP-2935 and reach Site-81. Extraneous and non-partner dialogue has been removed. For full records, please contact the Site-81 administration. Begin log. Extraneous dialogue removed. Team located several vehicles and began to move south towards Site-81. Main roadways are navigable, due to few vehicles being on them at the time of the aforementioned total death of all lifeforms within SCP-2935. Several fires are visible from the highway, including three downed jetliners. Examination of crash sites show a recurring theme. All inhabitants seem to lose consciousness at the same time. As a result of this, there are also few vehicle on vehicle collisions, as most of the vehicles stop simultaneously. Upon reaching Blumenten, MTF-E13 split into two separate teams, one led by Agent Roy, which would move directly to Site-81, and another, led by Agent Juno, which would attempt to access the offsite Deep Storage Server Bank. For the purposes of this log, Agent Juno's team logs are omitted. Some gather from their excursion can be found in Addendum 2935.3. Agent Roy's team approached Site-81 main access point beneath the Lake Monroe Reservoir Dam. Access elevator is confirmed as operational, and the team descends to the entry level. Roy. Yeah. I was wondering. I know you guys were on assignment, but I think I was on site on the 19th. I was thinking the same thing. I was on site that day, too. You think we're in here? We'll find out soon enough. I spent the entire night in the weapons lab with Foster, Morocco. It's right inside. You guys hear that? Hear what? Exactly. Shouldn't we be hearing a breach alarm? Not necessarily. Breach alarms are automated, but only if any of the containment cells trigger it. Otherwise, they have to be executed manually. Somebody had to have gotten to the office to start the emergency broadcast. It was an automated response. If I had to wager, it was probably triggered by vital monitors going flat. Vital monitors can trip the emergency response? Not anyone by itself, but a lot of them could. Here we are. The team departs elevator. Primary access gate to Site-81 is visible. All lights continue to function. Lockdown status is visually confirmed. Keller, get that door open. Careful, everyone. Agent Keller interfaces with access console. Lockdown status is rescinded. The main gate opens. Team moves through check-in area. Coast is clear. Alright boys, let's check the front offices first. Head right. Team enters Site-81 front offices. We got bodies over here. Yeah, we should expect a lot of that. Anybody recognize them? I mean, they're really dehydrated, but that's Desiree Clark and Max Westminster. John Cabin over there. This one is Alyssa Watson. They're all staffed at 81. They're probably working that day, too. Anyone know what time they mark off their calendars in the office? Not until first shift shows up, 8am local? Makes sense. Last check-off is April 19th. Keller, package the system again and try to find out what triggered the emergency broadcast. Omen. You and Indigo, go check the break room over there. See if… I don't know. Boss? Sorry. Shit. I wasn't expecting this. Not like this, anyway. I thought it would be messier. Which as usually are, but this is… clean. I mean, they're pretty obviously corpses, but they're clean. No blood, slight post-mortem excretions, but it's all dried up at this point. Think it was a disease? Let's get some samples. Swab surfaces use Indigo's kit to check for microbes. Juno's boy found a house without a trace of them, and Command wants to know if that's consistent. Be careful not to contaminate any surfaces you're collecting from. Keep your suits on. Don't de-glove, etc. Right, let's move. Radio in if you find anything. Will do. Agent Omen and Indigo moved to break room. Several other corpses are discovered during examination of the area. Agent Keller interfaces again with the Site-81 control system. Agents Ali, Strait, and Daniels leave front office and collect samples from nearby cafeteria. Got it. What's it say? Looks like the system was triggered at 0400 hours during a routine vitals check. Probably there was a malfunction, or rather the system thought there was a malfunction. All the vitals transmitters had stopped responding since the last check. That doesn't throw up a breach alarm? No, I don't think so. It would probably ping maintenance first, and then System Command, and then Site Command. If nobody responded, it would probably trigger a message to 17, and if that would ignored, maybe Overwatch Command? After those all timed out, it dropped into the automated failsafe, locked down the site and began broadcasting for help. Then it waited. Waited for what? A response from another Site, or literally anybody on staff. I think even level 1s can rescind timeout lockdowns. Hypothetical though, I've never seen it used like that. So nobody came calling. Nobody but us a couple days later. What about the AIADs? Alexandra's patched into the site and she, maybe they're still here. Good point. Pauses while interacting with Terminal. There we go. Alexandra.aic is currently running. That's good. I'll wake her up. Pauses again. Alexandra, can you hear me? No response. Alexandra, this is James Keller. Are you awake? Try the text interface. Interfaces was Terminal again. Nothing. It says the program is still running, but no response at all. I'll try… Huh. Nothing from Thorne either. They've all gone quiet. That's odd. Will us being here wake the other sites up since we rescinded 81's lockdown? Assuming they're all in the same lockdown as this one, maybe. No doubt some of them have protocols that require somebody to be on site to break a lockdown. I know Site-27 does, but they've got a pretty substantial Keter wing. Of course we could get the Overwatch and unlock them that way. I know they can remotely rescind security measures at all the sites. Do you know where Overwatch is? No. Do you? No. Hey boss, we're, uh… Where are you, Omen? We're in the Weapons Lab. Ah. We could just collect samples and lock up after. No, I want to see it. We'll be right there. Agents Roy and Keller moved to Site-81 Weapons Lab. Agents Omen and Indigo stand just inside the door. Let's have a look. Boss, we… It's not me in there. I am me. You think I'm worried about what happens inside of an anomaly?  Places that mess with your head or whatever. Taking my own corpse isn't going to ruin my day. Team enters Weapons Lab. Agents Morocco and Foster lay in near a lab bench. The corpse of Dr. Rogers is collapsed near the doors of the firing range. Room is otherwise empty, though covered in dust. Where is it? Agent Omen leads team to the door of the firing range. Inside the range is empty, except for a single corpse at the far end of the room laying on the floor. We've collected samples, and I got a chance to look at a few under a scope. One hundred percent sell death at every single one. We'll have to get these back to bio in order to do a more thorough investigation, but never see anything like it. Yeah, we will. Agent Roy poses over the corpse of Agent Roy. He reaches down and turns the corpse over, revealing the firearm that Agent Roy had been testing. They're… obviously not rotten or anything. You could barely even smell them. None of the biological processes that break down a body after death seem to have kicked in because, well, somewhere along the line they're stopped being biological processes. They're just dried out now. I see that. I remember this. I was only testing this for a little while. They'll be able to find it on security footage, nail down what time this all happened, see if it's consistent with everything else. Right. Okay, so we should probably check on our senior staff. I think Dr. Atkis likes to get to bed by 9, so he'll probably be in his quarters. We're already there. He's gone. The rest of them are too. Dr. Hamilton, Dr. Love, Dr. Karsten, Dr. Mann was out in the hall. I think he was in town for that seminar on the 19th. They're just like all the rest of them. Totally undisturbed otherwise. Saves us that trip, I guess. Keller, get into that terminal. See if we can access the containment wings.  Can do. Agent Keller moves to a nearby terminal. Agent Indigo collects samples from the corpse of Agent Roy. Elsewhere, Agent Strait, Ollie, and Daniels examine the corpses of the Site-81 senior staff, collecting samples as necessary and taking artifacts for local observation. You guys get the feeling we're getting mind-whitered to re-get back from this? Why? This has to be a huge breach of informational security, right?  I could go look at Accus's sock drawer and tell you whether he prefers boxers or briefs. Who knows what else we could get into, accidentally or otherwise. Senior staff doesn't have as much factual knowledge of the skips of their site, believe it or not. The important stuff is locked down in the network, and the really important stuff is kept on vinyl somewhere. Regardless, you don't need to go snooping through his journal or anything. Actually, I take that back. If you come across a journal, pick it up. Wouldn't hurt. Amnestics hurt. You won't know either way. I'm in, boss. Looks like everything should be clear, though we'll have to access a handful manually. I can't open them up from here. Should be pretty straightforward and… yeah? Sort of. I'm not sure what I'm looking at. It's an encrypted security warning, but it wasn't triggered automatically. Somebody would've had to put it here. When was it posted? About three days ago. So definitely after our projected date. Could very well be a glitch or something, but… but… it's not likely. These kind of things just don't show up. Too many fail-says. The system won't throw up an encrypted message unless it's absolutely necessary. Or somebody put it there. Keller pauses. Video and audio recording equipment cuts out briefly. Right? Right. Log it, transmit it back to Juno's team, have them relay it local side, see what they can make of it. Sure. Just received a message from them. Looks like they've finished up. Says we're going to roll our way here in a bit. Alright, let's head downstairs then, see what the skips have been up to. Team assembles outside of staff dormitories. Team moves to lower level access elevator. Team arrives at first containment level. Wait it's about you boys. I feel like something is watching us. I feel it too, doesn't feel right. There's something else in here.  Team begins to check safe-class containment cells. SCP-2151, that big fleshy thing. Get that door open. Agents open the door. There, in the corner. Is it moving? It looks like it's moving.  Agent Indigo examines SCP-2151-1A. Yeah, this one is gone. Check that chamber. The ring should be in there. They're in here, they're all tarnished though. This one is rusted though. Bag them, let's move on, what's next? That displacement chamber is at the end of the hall, we should check that next. The ghost girl is in there. Let's see. Wait, this cell is lit up too, doesn't have a designation tag on it. Fuck, can you smell that? Is it coming from this room? Smells like death. God, that's strong. Can you get that door open, killer?  I think it's jammed. Maybe a malfunction. Open the window, it's not jammed. All he opens window. Oh fuck, that one's decomposed. Christ alive, you're right. Why is it so much different? Who is that? They've got on a jacket. Hang on. Oh man, killer, that's you. You're sure? Agent number 1703, yeah. The name badge is, uh, covered. But you can see the ID number on the other sleeve, see?  I am… I'm actually not sure. I definitely wasn't on site on the 19th or 20th. That's really weird. We'll come back to it. Let's keep going. Team moves down to SCP-2996's containment cell. Isn't this that skip that, yep, did they ever get that resolved? No, not as far as I know. Agent Stray opens the chamber door. Fuck. Is the displacement chamber still functional? Looks like it. So what's that over the inside of the chamber? If I had to guess, I'd say that's the ghost girl. Did she explode? Maybe had an adverse reaction to dying twice? Can we get the chamber open? I'd advise against it. Our suits aren't rated for whatever's in there. You should see the monstrosities they had to wear when they go in to clean this thing. Fair enough, let's keep looking. Team continues to check containment cells, all with similar results. All biological anomalous entities are confirmed to have perished, while non-biological artifact entities have become inert. This continues for an additional hour. Something just occurred to me, boss. Yeah. Did you get that memo a few months ago about them moving that skip to 19? The lizard? Yeah, I was assigned to that job. It passed through 81 the way there. It did. Was only there a few days. Wait, what lizard? Which days? Downstairs, come on. Team moves to lowest containment level. Agent Keller rescinds lockdown status on the containment wing. Containment cells are rated for Euclid and Keter class entities, but are empty. They moved the lizard here, and didn't tell sight staff? Only essential personnel. Staff tends to get nervous. Huh, wonder why. Quiet. It'd be just around this quarter, there. Team faces the containment cell. Green indicator light is lit, indicating that the containment cell is active. Get the door killer. Hey boss, hang on. If we open that door and it's still, you know, the way it usually is, then we're fucked, I know. Motions to killer. Agent Keller opens security door. Team enters containment cell. Within the cell is a large steel container. A tank of acids hits above the tank, as do several other containment-oriented machines. There's a door over here. Rory wheat. Agent Rory opens the door to the container. Now is… The corpse of SCP-682 is visible within the chamber. Entity displays no signs of life. That's impossible.  There's no way. Agent Indigo approaches the corpse and proceeds to examine it. After a short time, he steps back. Yeah, it's dead. Team remains silent for a moment. Agent Ollie runs his hands over his head. You know, I'm suddenly feeling weird about this place too, boys. Let's get topside. Do you want me to collect some samples? It can wait. Team returns to the surface. Little is discussed on the way. Team rendezvous with Agent Juno's acquisition team. Both teams dispatch automated drones to the SCP-2935 access site with collected artifacts and information for local analysis. End log. Exploratory mission 2935.3 Codename 19 Mission Abstract The travel to and ascertain the condition of Site-19 within SCP-2935. Assigned Task Force Mobile Task Force Epsilon-13 Manifest Destiny 16 Members Additional Information The following is a transcript of audio and video recordings captured by MTF-E13. The 16-man recovery team, led by agents Juno and Roy, were given instructions to extend their mission within SCP-2935 and travel to Site-19. Begin log. Due to a technical issue with the recording equipment used by the MTF-E13 team, all but one recorder failed to transmit to the broadcast relay. The remaining recorder, belonging to Agent Keller, continued to intermittently transmit audio only during the entire duration of the six-day expedition. After the first day, Command was able to relay with Agent Keller and inform him of the state of the transmitters. It is believed that Agent Keller received this message, although not certain as Agent Keller made no attempts during the mission to attempt to repair the transmitters. The following are excerpts of Agent Keller's audio transmissions. Southwest of here. Hang on. There we go. There are a lot of system messages in here. Looks like a lot of sites were trying to automatically contact 19 for assistance. I think some of these sites I haven't even heard of. That one might even be… same as the transmitters of 81. Yeah, but this one doesn't do an hourly check. This pings them all every few seconds. Zero-one-thirteen hours. So that would be Zero-three-thirteen Eastern Standard Time. That fits in our projected timetable. Power failure. There's nobody down there that changed the fuel cells, so I'll probably just shred them and wait for new ones. No lights until then. Not the right kind of engineer, sorry. Should be one down the hall. Yeah, he's dead. I assume since I'm still standing here, it's not working anymore. All you have to do is touch it. Bag it. Throw a sticker on it. Let them know the amulet won't do anything to them. Hang on. Door's up. I think that used to be Dr. Sumerian. Over here's Agent Straight say, that was a bad place to stand. Understatement of the year. I'm having trouble getting… our connection isn't great down here. Broken. Just like the mask was earlier. Haha, no you can blink, it's fine. Looking to sell. Hello SCP-079? Are you awake? Nothing. That answers that. What were you expecting? Drones here. I'm going to go send it back to the access point, it'll just be a minute. Several minutes of Agent Keller quickly typing at a keyboard. Unlike previous transmissions, no other individuals can be heard in the background. Just checking to see if there are any other messages we should know about. No. Nothing out of the ordinary. We're good to push on. At least you look good, man with face down at the bottom of a flight of stairs. They're all dead. Every single one of them. How haven't you figured this out yet? We're not on a goddamn recovery mission. We're not here to rescue anyone. There's nobody to rescue. Our evidence indicates that everyone… No. Everyone. Everyone is dead. Everyone and everything. 100% of Foundation sites report the same transmitter malfunction. 100% of Foundation sites in lockdown. Not just here, all over the world. There's no bunker they could've gotten to. No. Because it was everybody. But this isn't our reality. It's somebody else's. Ours is… It's fine. Nothing happened to ours. That's the power core ejecting the spent fuel rods. Lights out. It must've triggered an emergency breach protocol. I can't. The door is locked. Juno, I just can't magic it open. I'm sorry, I'll try to get something out. Hey, Command, this is Keller. The on-site nuke at 19 got tripped. We're locked in down here.  And Daniels has family in Florida. Just let them know he's alright. That you're gonna be alright. Roy has kids. He says, you get it. No, just means the loudspeaker lost power. We're done. I'm… Transmission cuts out suddenly. End log. Summary Mission 2935.4 Code Name Emptiness Mission Abstract To utilize an automated drone to assess the situation of the SCP-2935 reality at large, as well as recon with the MTF-E13 team at Site-19. Assign Task Force, not available. One automated drone. Additional information. The following is a transcription of the audio and video recorded by an automated Foundation drone, SKF-1951, launched by Site-81 personnel at the SCP-2935 access point. The planned mission was to use the drone to gather information about SCP-2935, as well as to contact MTF-E13 and retrieve artifacts and data collected by the team. Begin log. Drone moved from access point onto nearby road, which it uses as a runway for takeoff. Drone ascends to an altitude of three kilometers. From this height to surrounding areas clearly visible, the entire region is completely devoid of all forms of biological life. Many trees have collapsed, likely due to high winds, and large drifts of sand and dirt are beginning to form along roadways and houses. To the west, a storm system is forming moving east. The drone turns east towards Indianapolis. As previously confirmed by MTF-E13, US Highway 70 is mostly empty of vehicle traffic, safe for the occasional semi-trailer. Several large fires have broken out across the dried vegetation and buildings in nearby towns. In the distance, the Indianapolis International Airport is visible, with several other large fires nearby, likely due to downed planes. A large pillar of smoke obscures the camera briefly, and after passing it is confirmed to have originated from a downed Southwest Airlines 737 jetliner. On approach to Indianapolis, the city appears relatively unscathed. Several small fires appear to have broken out, but have either burned out or been put out by rain. One apartment building on the near west side appears to have collapsed, but most other structures remain intact. Drone turns north towards Site-19. Passing over the central north of Indiana reveals much of the same. Dead vegetation, dirt, and sand drifts, and the corpses of animals in livestock and area farms. Occasionally a human corpse is visible, though many likely remain within their homes. Camera cuts out, command is unable to re-establish link with drone, although this is not unexpected. Drone continues to fly autonomously towards Site-19, with the communications likely disrupted by the storm. Video link re-established. Drone now in the middle of thunderstorm, offheading slightly, lightning strikes nearby, and camera cuts out again. After half an hour, video link is re-established. Drone begins to descend. GPS determines that drone is nearing Site-19, roughly 35 km northwest of Lansing, Michigan. To the far northwest, a large fire is visible. Below, another jetliner is visible, having crashed into Spartan Stadium at Michigan State University. A fire burns on the Red Cedar River just north of the university. Drone begins final descent, closing in on the Site-19 compound. After clearing credentials with Site-19, the drone lands on the northeast airstrip near the Staffed Dormitory Access Building. The drone then transmits its coordinates to the MTF-E-13 team, deploys solar panels and powers down. Five hours pass. Drone is activated by Agent Keller, who proceeds to load a parcel of collected artifacts into the underside of the drone. Agent Keller's radio is heard receiving communications from his team, although the messages are unintelligible. Lastly, Agent Keller loads the drone with a large amount of recovered data from a recovery team hard drive. Agent Keller then crouches in front of primary observation camera. The Agent reaches forward to clean the camera off with the back of a glove and then stares into the camera. I don't have any answers. I don't think there are any. I'll do this one thing and hope that fixes it. Seal it shut. You've got to lock it in here with us. I'm sorry. Agent steps away from Drone and returns to Access Building. Ten minutes later, Drone departs for SCP-2935 Access Point. Only two hours into flight, Drone detects a large explosion in the direction of Site-19. Mushroom cloud indicative of an on-site nuclear device being detonated is visible on the horizon. Return trip otherwise uneventful. Drone recovered on local site of SCP-2935 without further incident. Artifacts and data moved to Site-81 for investigation. Addendum 2935.3 Recovered data and artifacts from MTF-E-13 missions Note, the following in the list of artifacts recovered by the MTF-E-13 team on its three separate missions of the SCP-2935. Some artifacts omitted. See Site-81 Research Department for a full list of recovered items. For information about data recovered from SCP-2935, please see the additional section at the end of this addendum. Artifacts, recovery site, description, additional information. Sample of various vegetation. SCP-2935 Access Point. All specimens were severely dried out and confirmed as having no remaining living cells. Not available. Several various insect carcasses near SCP-2935 Access Point. All specimens were dried out and confirmed as having no remaining living cells. Not available. A copy of the Hendricks County Flyer dated April 19, 2016. Gauntlet House. Covered in dust, no signs of microbes or other living biological materials. Not available. Hair and skin samples from an adult male. Gauntlet House. Total cell death. Not available. Hair and skin samples from an adult female. Gauntlet House. Total cell death. Not available. Hair and skin samples from an adult female. Gauntlet House. Total cell death. Not available.  Gauntlet House. Total cell death. Not available. Cell phone collected off adult female corpse. Gauntlet House. Samsung Note 5 smartphone in white. Last communications sent from phone on April 19, 2016 at 2041 hours Eastern Standard Time. Message reads, are you guys still planning on playing cards tonight? I have Steven, but he'll probably be asleep soon. Foodstuffs. Gauntlet House. Dried out and covered in dust, but no evidence signs of decay. Analysis showed no signs of microbial life throughout any of the recovered food items. Not available. Desk calendar. Site 81. The desktop calendar is sitting at the front office of Site 81. Last marked off day is April 19, 2016. Covered in a fine layer of dust. Not available. Skin samples collected from various Site 81 front office staff members. Site 81. All samples confirmed with the experience in total cell death. No microbial life remaining. Not available. Various firearms collected from Site 81 fire in range. Site 81. Traces of oils from human hands, but no residual microbial life forms. Not available. Flesh sample from SCP-2151-1A. Site 81. Flesh sample unresponsive. Total cell death confirmed with the further analysis. Not available. Other bound journal belonging to Director Atkis. Site 81. Matches Director Atkis' personal journal to that date. No inconsistent entries noted. Move to storage. SCP-2151-A and B. Site 81. Both items are severely corroded. After further testing, both instances are confirmed to be no longer be anomalous. Both instances moved to storage. Skin and hair samples from Site 19 staff. Site 19. Disconsistent with other previous samples. Not available. SCP-963 Site 19. Artifact is inert. Instance of Dr. Jack Bright that the artifact was recovered from was consistent with other corpses found within SCP-2935. A smashed wristwatch belonging to Dr. Darius Hemsworth. Site 19. wristwatch no longer operational. Apparently ceased operation at 03.13 hours Eastern Standard Time after falling to the ground with its owner. Most pieces of concrete and rebar are covered in green and red paint. Site 19. Artifact is inert. The origin of this artifact is uncertain. Data acquisitions. Data source. An automated emergency response signal originating from Site 81 led to the discovery of SCP-2935. This is an automated emergency broadcast from the SCP Foundation and your national government. One or more of our sites is experiencing a communication breakdown, likely due to a containment breach of unknown magnitude. All citizens are ordered to stay in their homes as the containment teams work to secure the breach. This message will broadcast from April 20, 2016 until… Message cuts off suddenly. Data source. A log of the stress pings originating from Site 81. 03.13 Massive Transmitter Error Requesting Maintenance 03.14 Massive Transmitter Error Requesting Maintenance 03.15 Massive Transmitter Error Possible breach of containment requesting maintenance 03.16 The Site 81 Command Massive Transmitter Error Please Advise 03.21 The Site 81 Command Massive Transmitter Error Please Advise 03.26 The Site 81 Command Massive Transmitter Error Beginning Lockdown Procedures Site will lock down in 10 minutes 03.31 Site will lock down in 5 minutes 03.35 Site will lock down in 1 minute 03.36 Site locked down in complete Please Advise 04.00 The Site 17 Command Site experiencing Massive Transmitter Error Lockdown Procedures initiated Please Advise 04.500 The Overwatch Command Multiple sites unresponsive experiencing Massive Transmitter Error Lockdown Procedures initiated Please Advise Data source Site 19 Interior and exterior security camera footage. Footage shows the exact moment during which the SCP-2935 event took place. At exactly 03.13 hours Eastern Standard Time, footage shows all members of site staff on camera as well as all surrounding flora and fauna outside of Site 19 suddenly dying. No other phenomenon are evident in this footage. Data source Encrypted security warning recovered from Site 81. Decryption of source revealed a hidden audio log file. Transcript of that file is below. All right, here we are. My name is, you know, it doesn't really matter. I am on, was on staff at 81. If you're hearing this and you've probably got some idea what the deal is here, so I don't need to explain the foundation to you. But this, everything else? I mean, it's pretty self-evident, isn't it?  As of my recording this, it is 21-36 hours Eastern Standard Time on April 26th.  I wish I had an explanation. If I didn't still bleed, I would think I was dreaming. I've had dreams that I was dreaming, but I wake up and I'm still here, still here, alone, and everyone is gone. They sent me to check this signal they had picked up in their Joppa, just off of 70. Quick little exploratory mission. I was the closest. I pop in there and find this cave, and on the other side is the world I just left, but it's this one. This is the world I ended up in. The grass, the birds, things dropping out of the skies, and dark things floating in the water. People everywhere, lying where they stood, and the silence, God the silence. Not even birds or bugs just wind, and nothing else. I came back to report on what I had seen and… I don't have any answers. I don't think there are any. I don't even have the right words to say. This world is different from the one I saw in the cave. People are moved around. The date is different. Things are different. Because it's my world. This is the one I left. This is… my family is here and my friends. But now… It's all gone. Everything is dead. There's no evil magic. There's no supernatural stars. There's no futuristic ray gun or false vacuum device or… nothing. None of those things mattered. Nothing we did mattered. It's all gone. Something. Something must have been in that cave. Something must have followed me out of there. Needed me to go in there. Needed me to bring it out. Let it loose. Let it do to my world what it did to… to that. Maybe it's me. Maybe I was the reason. Maybe I am death. If it was in there, and I brought it back, then I am death. I've got myself in a containment cell. Jam the goddamn door shut. I'm going to put a bullet between my eyes. Everyone else is dead. Watch one more. You know what occurs to me? If you're listening to this, you're death too.


Currently I'm in Copenhagen. I love this place. Everyone here just seems happy. Everyone. The only problem is that I sort of forgot to book a place to sleep for the night. So I went to a Wi-Fi spot and asked the crowd for help. And this guy replied. But the weird thing is he doesn't know or follow me and besides this tiny picture. I have no idea who he is. But sure, sounds nice. So currently on my way to the apartment. We're kind of in a rush because he's leaving for a birthday in half an hour and he seems like a good guy. Hopefully it's not one of those catfish moments. He should be there. Kenneth just left to his party and now I'm here all alone in his apartment. And he gave me his keys so I can do whatever I want. His place is really neat. Cool stuff lying around, lots of interesting things and a nice view. However, that doesn't make this a story worth sharing. But this does. See, Kenneth, the guy, he had to leave in a hurry for the birthday and he didn't have time to clean his room. So everything was still lying around here. Also valuable things like this insanely thin MacBook or his memory cards with probably some private pictures. His mail and even credit cards. It was like I ended up in the fantasy of a thief. He has no clue what I'm going to do with this stuff. But he just has trust in people.  Finally, I flipped through some of his books, watched the office for the 25th time and went to bed. That morning, after a very good sleep, I hopped in the shower, brushed my teeth. We got to know each other. I gave him a huge thanks. Alright, thank you. I went home. Well, that's good.


Hi everyone, I hope you're all well having a good day. Thank you so much for tuning into another episode of Pokemon VGC 2019 battle series. We are here again today kicking off and continuing on with this x-ray team that we started playing last week on the channel If you missed any of the games from last week or yesterday even you'd like to go back and check those out Go up here link a card for you You can check those out before you come into today's episode and continue on with some more really good games So as I said at the start of the week in yesterday's episode What we're gonna do is we were kind of toying around with the idea to maybe change up this call as we go into the end of this week But we'll see how this team plays out because we're on pretty good terms with the team We're having really good results with it So if we continue with that we'll play it out till Friday if not We might change it up and if we don't feature some of the other XY calls that we've been talking about Throughout the last week then we will feature them on the streams and maybe some other things that will do outside of that But just to recap the team as well It is down in the description below with a roll pace and a poker pace for you guys to check out try out If you'd like to if you do let me know how you get on with the team But to recap we've got the Rayquaza, which is the mega of the team got the zernius the lander's theory And it's got the Z move the tapu finny incinero and Serena so without further ado guys Thank you so much for tuning in. We'll jump straight into it. So I'm looking forward to this today We didn't have the best end to yesterday's episode, but it was a really nice way to end It was a nice team to play So we'll click in some music and as always guys if you enjoy this sort of content Do remember to leave a like on the video really helps out the channel do subscribe to the channel for more Pokemon content and Also leave your comments in the comment section because I love hearing from you all and I will get back to you as soon as I am Able to so hopefully it doesn't take too long to find our first opponent of the day if it does as always I'll just cut out and we'll come straight back in where we bump into our first opponent and We have our first opponent of the episode. So we're going up against the Japanese ready player. I think 1594 more hop straight into team So first opponent today is running a team of Gerardo and tapu finny incinero ferrathorn cangas corn and that dawn wings necrosma So is it dawn wings or is it ultra necrosma? Who knows they could have trick room now because this team is quite trick room kind of scented There's not really any other speed control on the team. You can identify other than maybe I see wind on the tapu finny So indication is that it probably is more than likely a Trick room team and maybe it's not done Ultra necrosma. Maybe it is just dung wings But what are we gonna do? Obviously incinero is really great here for the ferrathorn the the dawn wings the ultra necrosma Whichever variant it is the intimidates amazing for ground on incinero and cangas corn as well So we definitely want our incinero I think as well like landerus is pretty nice here to be honest and we could bring tapu finny landerus and do we want Requizer or do we want zonius? I Think Requizer is better here thinking our match yesterday One of the things that I feel like we probably did was force a zonius when maybe landerus would have been a better choice For us in that kind of build especially against primer ground on and just having that option there to deal with it And double intimidate as well. It's always useful when when a team so heavily based around physical attackers So we'll lock in with these and get into our first game So good luck to my opponent in your very flowery pink shirt that you've got on today And that's hope we can make up for that that that loss that we had yesterday because I Kind of was enjoying the run that we were on with the team, but it's still doing super well So hopefully we just continue that and we just need to not get ahead of ourselves No, think about the school think about the Pokemon think about what's in front of us and just go from there So we see the Dawn Wings and of course Matt and tapu finny come out from my opponent And we'll get the intimidate off with incinero Think one of the things that rather do than fake out here I could snarl for sure, but I kind of tempted just to you turn out on the tapu finny and go for Dawn Wings is likely to protect us in it. I don't want to get trapped in just take How could we it the damage onto the necrosma might be quite nice if we do go for the u-turn there and then Go for an icy wind. Yeah, we'll do that Necrosma switches out, which is fine ground. I'm gonna come in. It's also alright Because you get the icy wind off, which is really really good for us because one of the things we can try and bait My opponent in with this next turn is a scald Switch to ray on that ground on which we've not been able to do yet Which would be really nice if we could catch my opponent out with So there's our icy wind. You do have to beat the tapu finny So even if we get icy winded we'll know that we should be faster than their ground on tapu finny the next turn There's the icy wind back in return And we'll just get a bit more chip damage onto that ground on which is always helpful because Most of the time the skull is it's got a high roll, but it is a roll and The more damage we get into this ground on right now. The better chances are to get it with a skull So I don't know if I want to bring in Requiser yet might bring in Hmm. No Might bring in landers get the intimidate onto it. Yeah My DS will load come on. Yes. Okay. Yeah, so landers got a pretty safe switching here We can switch out Get the intimidate onto that lander that that ground on And bringing in the problem with bringing in Ray quasi obviously is taking a nice wind When we have just got the tectonic rage that we could launch into the ground on right now That's the big thing because I feel like we're probably forcing the ground on out almost anyway So we could preserve this for later and not bluff it right now and just go for another icy wind And the ground on is gonna be minus two by the time the incinerole comes in And I think the ground on probably protects here as well So the next turn is where we could potentially Probably not because the icy wind will probably Now the ground on is forced out so that's good and you see them across my come back in no It's gonna be the ferrethorn. All right. All right, so we get that speed drop again. No, that's the wind coming out But we're putting a heck of a lot of pressure onto this ferrethorn this this turn The one thing I probably want to do I Don't think the ferrethorn attacks into Finney honestly, I really don't see it Because I'm kind of tempted to go for the flablets into the ferrethorn honestly, but I think it's not early on in the game I don't think my opponent risks it Although if we don't go for it and we don't punish that then that's kind of our own fault, isn't it? I'm gonna go for the flablets And I'm gonna go for another icy wind So the type of finish which is that what we're gonna see come in the Krosma I wonder if we do see the the Ferrethorn, yeah, it's not protecting so this is what I mean like opponents just assume that You're sitting in front of an incinerole. I'll probably be able to get it an attack off But if you don't punish that that decision then then fair credit to your opponent because you're you're allowing them to do that And we're just checking that here. I know the the worst thing that we've got going into this next turn is that The groudon gets a free switch in which we don't really we don't Kind of want it to have but at the same time we do still have the player where we can switch in And Rekwaza and go for that Skald Although the groudon probably precipice blades when you take a photon geyser in the process it's not ideal We can pull it double switch Sure It's just if we can get this groudon I just don't think because precipice blades are getting incinerole so you probably go photon geyser Precipice blades into the finny that would be my best bet I'm gonna bring in Rekwaza. It should be pretty safe coming in here And I'm gonna actually try for the Skald into the groudon Problem is taboo finish so slow at this point. So we're not really gonna be able to I'd speed the groudon Which is a little bit annoying because normally we get the jump on it So this would be an easy decision. We know that an acrosma can't go for it Z move here Do you have that on our side photon geyser? Yeah, it's gonna be into a finny. I'm gonna press with blades and I think Maybe we take it maybe I Don't know though. I don't read It's hard it intimidated we would yeah, but I'm intimidated. We're not taking that right, okay And now do we bring it in cinema? Yeah, yeah, we do Yep, we bring in cinema fake out ultra and acrosma and we sold stance And then we've got access to that really Super speedy extreme speed that will be able to deal with the ultra and acrosma Yeah, we'll do that sold stance. You gotta remember that the incineros in the back for my opponent as well So it's not massive. It's not straightforward at all. And the thing we could have done maybe here to capitalize on is sold stance Switching cinema out into lander us There's the alternate. I mean, oh, it's a course. It's a finny. It's not the incineroar. Is it?  I would imagine so But then we've got all ground arms actually allowing us to get the sold stance up for nothing That's dangerous dangerous because the finny goes down the next turn now You switch out incineroar into lander us And then we've kind of got a checkmate situation almost and with the incineroar on the back It's the perfect thing to keep in the back on ultra and acrosma comes out into the field because they can't really go for the earth power into either a requiser or Lander us they've got to go for the photon geyser if they've got it And that means incineroar is a great switching so it makes it a bit more complicated for my opponent to kind of close this one out for them at least but We'll go for the finny now. We should be able to pick up the knockout onto it We'll get another intimidate onto that ground on which is super super good And there's the dragon ascent Yeah, you take down the finny. I mean the ultra and acrosma comes in it will go down to a plus two extreme speed or an imagine I should do There's a precipice blades. Yeah And we still got a sash on a record a requiser as well. So I mean that There's really very little my opponent can do to deal with it now I'm like all we do now is just switch out lander us into incineroar, and then we've got the end game I mean the worst thing would be if My opponent protects the knock out and attacks into the ray But then if they do that we've got the fake out attacking to them the next time So I mean any way around it We should be all right and especially with landers in the back to come in and use a z move on the ground On to close down the game. It's gonna be fine. It's gonna be fine. There's a dragon pulse We'll take us down to a sash And then we'll get the dragon scent and imagine we'll probably see a fire punch into the requiser here Well, you might be worrying about the lander I see it's hard because everything kind of threatens the ground on at this point And you just don't have the resource to kind of deal with what's on the field There's a fire punch is it gonna be into yeah, okay, then now we're cause I can just deal with the ground on pretty easily We could fake out sword stance again, but I don't think we need to show about as much we can just go for Oh, let's click in right a dragon ascent and a fake out We might see a protect here But we just said the forfeit so very good against my opponent and a nice way for us to kind of open up the show today Yeah, it's an interesting matchup. I think The big thing about playing the requiser most of the time is making sure that you're keeping the sash intact on it Because once you get it into that position where the sash is intact and you've got a sword stance up You've got almost two turns to kind of really rip through quite a lot of Pokemon and most of the time with The additional support still from fake out from the incineroar and I see when support and intimidate support It's normally enough to kind of close games out. So it's good. It's good. We'll look for our next opponent We'll get some music on In homage of ultra necrosma. Should we go? Ultra necrosma version 2 it's always a good one I feel like I might be playing it a little bit too much though recently, but we're not playing it every game So that's always a positive isn't it as well, right? As they say hopefully it doesn't take too long to find the next opponent if it does guys I'll just cut out and we'll come straight back to it and we've got an ex opponent of the episode We've got eyes in from Spain. So let's go straight over to a team preview screen And eyes in is running a team of Kyogre to go tomorrow incineroar Gengar and Rayquaza and Criscellia so we've got a combination of the Rayquaza and Kyogre here We've got supporting cast of mega Gengar She's going to be dangerous because it can trap us in and cause all sorts of problems You've got to go tomorrow there gonna be a fast faker Pokemon lightning run potentially also that steel typing so prone to carry the steel EMZ as well So we need to be careful with this Zonius around it and the incineroar with the faker and intimidate pressure and then the Criscellia is going to be the main Trick room set on this team and outside of the Gengar that has got access to icy wind and then trick room Criscellia is going to be there probably that the trick room set out of this team to support something like the Kyogre Now what are we going to do against this team? Obviously because there's quite a few physical attackers on the team I do want to intimidate now which intimidate I would I like more than any other? I might bring both to be honest to this game although it does leave our options a little bit Stretch I don't know if I want Zonius in this game though I might feel I feel like I want to go with exactly what we had in the last game to be honest With the lander us now Incineroar requires that Finney and lander us. Yeah, that's what we'll do Feel bad. We keep leaving out. There's only us all the time We keep leaving out the poor thing But we did this early last week and then it just came back with the vengeance and just started kicking butts so Yes, we'll see if we can bring it again and do some more devastation with it in our next episode So there's Incineroar requires it for ourselves and we'll see Gengor Gengor Gengor Criscellia, okay? Hmm we can fake out Criscellia prevent any speed controller We could drag in a certain Gengor to be honest because of our sash and I feel Honestly like it's probably worth it just to get rid of the Gengor with how annoying it can be to deal with and the position that it's gonna put Pokemon in The problem is is if the Criscellia goes for a helping hand But we've got the sash so it doesn't really matter The only thing we could yeah, I've got to fake it out because I don't want a trick room going up. No way And we can drag and send the other thing is we could potentially sword stance, but I don't think you Allow or requires a room to protect this first turn. I think you've got to attack into it So let's see what my opponent does We do mega evolve Gengor is not mega evolving which is really interesting or if it is it's very slow There's a fake out into the Criscellia Dragon is sent is it sash Gengor and it's gone for trick room I have a horrible feeling that's what it's gonna do. I don't understand this. I don't understand I mean the cursed body is fine because we just switching requires are at the next turn anyway Oh, we're protecting it while we adjust our board position because I imagine the Kyogre comes in now all the requests are Just don't understand Maybe they thought yeah, I mean the Kyogre's coming in now. That's yep fine We have to protect requires a and I think we switch in signal out to tap a finny You might see a trick room here. I imagine my opponent's last Pokemon in the back is probably Probably requires a I mean we could have dragon and sent it here But there is the risk of a water spout it would get really in signal chip our session and an ice beam from the Criscellia especially with the The Delta stream gone now That could potentially lose us Requires and we're not gonna kale either of these targets in front of us at the minute So we'll protect as the ice beam. So finny getting a free switch in here, which is really nice There's an icy wind. Yeah, so we're not seeing a trick room, which is Maybe more of a positive than anything else now do we want to Sack and signal or land or us here That's the question. I think we've got to icy wind Whatever we do Hmm, I think kind of predict What do we bring in lander us Hmm, it's my opponent potentially got in the back It's gonna be the requiser I'm gonna bring in lander us to sack that I prefer to keep the fake out I think from in-center or around for a little later if I can We might see the cut Kyogre go for something other than an ice beam or a water type attack Now it's gone for the S beam again. That's why the incineroar would have been good All under us there's another icy wind and let's bring it Think we need to bring in my quasi and then switching Finney out into incineroar Because I don't think there's gonna be a water type attack here And then we've got to fake out to get a soul stance of the next turn And I think that's kind of what we need to be doing To get in a little bit of momentum in this game So get incineroar in the one thing we need to do is Yeah, be careful around this this Kyogre for sure Probably gonna ice beam icy wind again Kyogre protects, okay, so it's definitely can't protect the next turn There's an icy winds Now we'll be able to take an icy wind from the Cresselia without Requiser because of the strong winds And because we've already got an icy wind onto the Kyogre It does put us in a position where we can still guarantee to outspeed at the next turn I think that's what we do Cresselia's a real pain to deal with though, isn't it? If it's Requiser though, we break a potential sash and although we will be slower than at the next turn To take away That's smart.  I mean, that's quite nice.  Legit top tier VGC mon and all right, so we'll bring in tapu finny We've still got our sash intact and Do we just attack the Requiser? I just feel like the Ray Protects him more than anything hmm because potentially we could just go for a U-turn out onto the Crest getting damage onto it as well We could actually double the Crest, but I'm just gonna I'm actually gonna go for the Dragon Ascent into the Requiser It is mega-revolving so it's not gonna keep the airlock on the field not interested in going for that icy wind It does it does protect that makes a lot more sense It'd be better chasing the Crest, but I mean Still all right. It's not over the speed drops not great But as long as the Kyogre is not out on the field the moment I Forget we were intimidated by the Crest with me. Yeah hmm Now one of the things we could do is It could heal pulse It's just very well We're gonna be slower than the the Requiser aren't me, but we have got the opportunity now to go for an icy wind if you want to Even up the score and just protect our Requiser Because that Requiser has just protected Yeah, it goes for Dragon Ascent into us. Yeah, I think it would be better gone for the finny there. I Thought miss Requiser there. They don't even care about missing the Cracella. What do we see the Cracella do? Toxic That is grim grim grim grim. That's not good. We need our terrain back up No good. No good. No good. No good. We just minus one. No, we're not minus. They're minus one. We're minus one So it's a speed tie right now Now we could go for the Dragon Ascent into the Requiser. I mean we're plus one, right? I don't think an extreme speed gets the Requiser from here, but we could heal pulse Our own ray. It's a little bit risky because if we lose the speed tie, we definitely lose And we've never won a speed tie before I'm just gonna go for it. I'm going for it I think we'll win It goes for the double protect. Oh my gosh. Oh, no, it doesn't double protect here. Sorry Yeah If we get toxic to you, that's gonna actually win again. He's missed the Requiser. No No miss. Kind of just cycle around Around and around and around, don't we? And this toxic's eating away. That's the whole time Hmm Now potentially here what I could do is just switching in cinder all and then just get rid of the ray because it's gonna go for It's gonna go for the Dragon Ascent into us now, but it might think it will protect this turn So it'll target the Finney which would be ideal So you've like that is a possibility because they'll think oh, well, we're just gonna go on to the protect the Requiser again We're gonna get icy-winded. Let's chase down the Finney this turn And if they do that, that's so good for us They might not as well Dragon Ascent Where you going into? No, it's into us. We should take this though. Oh I don't know if we're gonna take I don't know if we're gonna take an icy wind Hopefully that crest goes before us Or to life up as well Hmm, and then if we lose the ray here We lose to the Kyogre because you've got no way to deal with it. Once the icy wind It's taken down. It's because we left that Cresselia alone for so long. That's that's the biggest problem I see when my miss never misses does it? Come on Ray. Hang on Ah, and there's no way we can take down the combination of Cresselia and in and Kyogre now No We would have been better off just and I'd like that Cresselia We've done the same thing in this match what we did a couple of weeks ago now against the incineroar where we let it snarl and snarl and snarl in front of our Azonis we've just let that Cresselia just do what it likes in front of us and we can't really do much about it now Finney's toxic saw the time the The timers on that completely and all we can do is fake out And we can try for oh, we can't even get a burn because the Cresselia is on the ground now It's got intimidating not levitate So it's protected by the terrain Ah And you know like thinking like Xernius could have been a way better option here for especially against these two Pokemon And scalds aren't doing too bad damage, but we're gonna see another instance Yeah, swap intimidate for intimidate But it really doesn't matter at this point. I could just hit the forfeit button, but I'll give my opponent the benefit of the victory Even though it's cycling down so slowly I'm really disappointed by this. I am really disappointed by this, but I Think this is one we could have definitely won Cresselia is still a very good Pokemon in this format Very good Pokemon in this format. Let's go snow and let's go scald into Cresselia Hmm come on guy. Let's do this There's just no need to take this long really. I'm not complaining, but I mean It's pretty safe.  We'll get the berry No, our berry's gone. So that's fine Hopefully fins right now Skill swap stop skill swapping. I guess the crisis got nothing better to do at this point Yeah, this is taking too long and no one wants to watch this. So what I'm gonna do guys is just hit that forfeit button Say good game to my opponent. Oh, come on Finnie.  This is ridiculous I should have hit the forfeit button the tone before My opponent's one fair and square good game to them. We could have played a lot better There was areas there where we just let ourselves get Kind of overwhelmed by stuff and the fact is that we've just left that Cresselia alone for so long And just let it disrupt the whole time It's got to be something that you've got to like pay attention to and makes make not off those how many times we were sitting on plus two or even plus one with with Requires that where we could have just sniked it rather than concentrating down on that requiser on the opposite end of the field so much So by the bye. Thank you for tuning in though guys. I hope you've enjoyed today's episode We'll be back again tomorrow with more x-ray actions So do tune in for that. Have a great day morning afternoon whatever time of day it is and I will look forward to catching up with You all very soon. So until then take care and bye. Bye


Hello, we are back. Hello. And next up is parallel. So Simo, what should people get from this lesson? Yeah, what's how deep are we going? Yes. So this is quite a complicated thing to explain. So in this lesson, we'll talk about like, like parallel computing is all about like doing stuff that is like, you have multiple workers, multiple CPUs working together at the same time doing the same thing. Like in the area job, we have stuff that like they could happen at a different time at a different place, as long as they just happened, like you had, you had things happening that just needed to be done with a different parameter, but they didn't have to like have a communication. They didn't have to have like they didn't have to each of these jobs were independent, and they didn't need to work together. And in parallel computing, it's a different thing, because we want to like if if in the area jobs, we want to do more in parallel, we usually want to do faster, like, and more isn't always faster. Like, so so quite often, the most efficient way of getting stuff done is to do embarrassingly parallel all these areas, because like, if you do, if you can do like 100 simulations, like, if you can do 100 simulations separately, it's usually better than having 100 CPUs running one simulation at a time in a sequence. So so if we look at the analog of the pasta again, like, if we previously had just like these different kinds of pasta that we wanted to do, and now let's say we want to do like, we just want to do more pasta, like we could have like four cooks with their own own pots, do that thing, that would work like that, that that would work because like, like that would be the array job, we have four cooks there, cooking their things, and they all would produce one pot of pasta, and then we would have four pots of pasta, let's say. But we could also have a situation where we just add, we have one cook, but we add more, more pots to the to the stove. So we just do more with one one cook. And in that case, usually you get the same results, or you should get like, if it's if it parallelizes, like, optimally, you should get the same pasta done in the same time. But maybe like, when you're you have to move the pots around, if you're only one cook there, you have to move the pots around some of the time is wasted, because you have to do this kind of stuff. So it's usually not as efficient to do stuff, like just multiply, add more, more pots, add more stoves to a single, like, single, like job. Instead, it's usually better to do this embarrassingly parallel thing. But if you want to do parallel, you usually need to know what your program can do. Like, like it all depends on on the program that you're using. So there are two main paradigms that that are, well, in HPC, and in general, there's MPI, and there's multi threaded or a multiprocessing thing. And like, if your code has support MPI, it usually says it, it's like on the theme, like if it says that it's an MPI program, then it's an MPI program. And if it's not an MPI program, then it's not an MPI program. So then it's, it might be a multiprocessing program. And it's usually like hard to tell which one, or it might be hard to tell. But usually if you see something mentioned about like, MPI, then you know that, okay, it's MPI program. And if it doesn't mention MPI, but it talks about workers or number of jobs or a number of processors or whatever. It's usually the multiprocessing program, like the words get easily mixed up in this field, because like, everybody can use the words in which way they want. So there's no like, no one solution usually, like to recognize which program you're using. But when it comes to the resource allocation, the thing is very simple. If your program is multi-treaded, or is it, it's quite a multiprocessing, you need to specify the CPUs per task option to get multiple processors for the multiple CPUs available for the process.  I want multiple CPUs available. Can you provide them for me? And that's it. That's the end. Like, that slurm basically makes certain that okay, there's there are CPUs available. And then it just takes hands off. And then it makes certain that you have a big enough stove, basically, it makes certain that you have enough burners, enough working space to do your work. And then it's like goes off. But with MPI jobs, slurm does a lot more like it launches this kind of a world, a network between these many workers. So if you have to do like multi node, if you have to do parallel computing where you have multiple, like computers working in tandem together. So if you think about like a big weather weather model or something like that, you might have hundreds of computers creating this kind of own simulation that they all have to do. So this is like the traditional high performance computing, like, like which is still a very popular, which is like big scale stuff. That's done with MPI where slurm like gives each of these tasks, it gives them its own like own place to work. And then it like makes the communication between these tasks possible. And for those kinds of jobs, you need to use this end tasks option. So it's like two, one or the other, there are also hybrid jobs that use the both. But we don't want to talk about them here. It's too complicated. So let's just limit ourselves to these two options. So if your job is an MPI job, you need to talk about tasks. If your job is not an MPI job, you need to talk about number of CPUs. So just how many CPUs you can use. So let's, let's go and look at that example of an job. So this in the documentation, there's a lot of stuff about different kinds of like, what is a multi-traded multi-process that was asked previously, like, we don't want to go through that because it's technical and it's I don't think it helps. There's also talk about open MP, which is this kind of if you're coding, it's an easy way of getting like coding your multi-process stuff. But in most cases, you do something with an already existing framework. So here's an example of like Python, like this, this is also relevant for people who use Matlab or R or whatever. Those programs are internally multi-traded. So there's in Python, there's this NumPy library, which uses these other libraries that are all underneath them, they can utilize multiple processors. And if they see multiple processors, they use multiple processors. So that's how they work. Like if they see resources, like if you ever in your own laptop, you start some simulation, and then you notice that the laptop fans turns on, and all of your processors are using in use, that's usually because the program itself recognizes that there's multiple processors available. So if Richard, if you want to take the screen and show how to do this example. So in the example, there's like a simple like this, like, do this kind of like linear algebra, calculate pseudo inverse for a matrix kind of calculation that is done like multiple times. And then the timing is, it's timed like how, what is the, how long does it take to do this calculation? So if we just create a script, make it and just copy paste the whole code, everything there, I guess I don't even need to look at the code, do I? Yeah, yeah, like usually, like, if you just see that some programs supports multiple processes, you don't need to know how the sources it's made, it's usually like, like, if it's supported, it works. And we make a new script? Yeah, let's start with the script itself. Like if you like, let's not do that. Okay, we're doing great to script. Yeah, let's okay. Yeah, let's go straight to the script. There's an example of how to run it. No, like, so let's go straight to common pattern, we see we have a code and we have the separate script that controls it. Even though in theory, they could be combined with some effort. Yeah, so let's see. So L time tasks, two CPUs, one gigabyte. Okay. Yeah, so these also like this example, it might differ a bit different. If you're running in a different cluster, because they might be a different Python installation, they're available. But so what, what, what new do we see in this script? And the main like, and especially in the S batch section, like we see these two lines called CPUs per task and a memory per CPU. So, and we also have these end tasks set here, but you should you do don't need to set it. But basically, the idea is that you just want to have basically one of these MPI tasks, like the tasks number shouldn't be anything else than one. And you just want to have multiple CPUs available for the job. And in this case, we set two CPUs for the job. And instead of using the memory, that's just mem. In this case, we, we set a memory per a cheap CPU. So you can think of the total memory requirement for the job being the memory per CPU multiplied by the number of CPUs. So basically, and it depends. Yeah, like if you need to, if you want to use more CPUs, you only have to change one place instead of changing the memory separately, somehow. Yes. Yeah. In some cases, your program might be that that the number like they adding more CPUs doesn't increase the memory requirement of the job. In those cases, you might want to use a like a flat mem statement. But you can also use this mem per CPU. If you know that, okay, like if I add more CPUs, it will add more memory requirements. So you can have these kind of like helpers help the things here. But basically, what what this when we now submit the job, like the rest of the thing is like, we we just use Python via this anaconda module that has been installed. And then we when then we run the code. So that's like, that's something that that some program that supports multi threading. So should I so if we now, yeah, if you now submit it. Okay, it claims it's done. Yeah, if you look at the output, I'm removing all the Yeah. Okay, so can you see Python open MP dot out. If you don't have it noticed here, I push tab and then it automatically completes many of the things so I can type file names really quickly. Hmm. Okay. needs Oh, okay. The the script isn't like, yeah, can you can you do the VW gets comment there, like the Python command, like the Python script is only a partial of the script. It needs to import time. Yeah, it's missing some imports. Are there more? Yeah, you can download it there. Yeah. Yeah, I think it's import time and import number from. Yeah. Yeah, you can just download it. Should I just download it? Yeah, I think it's like in the example, there's like the command to download it. Yeah. Yeah, that's that's the unfortunately. Yeah, we'll have to update the example. Okay. There. So Yeah, yeah, if you're typing it along, then do notice that this the there's this download command. Okay, so now if you try it again, it probably takes a bit longer. Should we see what the differences are? Probably a waste of time. But okay, yeah, we see it's told in port. Yeah, that's several more things. Yeah. Yeah, that's our additional output. Okay. So, so there's also a question about like, like open MP, an open MPI. So this this kind of like a mess of like technical jargon in in HPC world. So this is open MP standard, which tells like, how do you come? How do you write code that does this parallelization using this open MP paradigm? And then there's MPI, which is this message passing interface, which is like, how do how do you do this message passing in later standard? And then there's open MPI, which is just like implementation of this MPI standard. So so yeah, it's it's like, it's the computer science world or like, yeah, like, whenever there's some somebody who who gets like technical days start to make up this naming conventions, and you have to like, this, this, it's unfortunate that you just have to like, spot the difference basically, whenever there's like, what are we talking about MP or MPI? And it's yeah, I don't know. So let's try it like it took 13 seconds. So so let's try with one CPU, how it would behave? Like what what would be the nano if we edit? Yeah, we need to nano the submit file. Yeah, one CPU per task. Yeah. Okay. So that, yeah. And as much it? Yeah. So, yeah, it will take a bit longer. So, so what's the important part is here is that, like, the requirements part, like your program, like, if you don't know if your program is capable of utilizing multiple processes, you can always try giving it multiple processes. But the main thing is then like to figure out where they actually utilize them. After this has finished, like if you look at the output now, 22 seconds. Yeah, so we saw like previously, it was 13 seconds and now it was 22. If you look at slum history for, for these jobs. See, yeah, we all yesterday, we already used this SF command to, to see, like how to monitor the like how the program was behaving. So if you want to run SF for, let's say the one CPU top first is here. Yeah. Yeah, the second one. Yeah. So, yeah. Yeah, in this case, like, we noticed that, yeah, it took 25 seconds to run. So that is the wall time, a wall clock time. And it used, used 90% of the CPU. So so with one CPU, it, this CPU utilization was 90%. So if we look at now the two CPU job that you run previously, like the SF of that. Yeah, the wall time is 15 seconds, which is less. Yeah, and the usage is more. Yeah. Yeah. So you can see that the it used to cause by node and the CPU efficiency is still pretty much the same. So it actually managed to utilize both of the cities. So if you're unsure if your program supports multiple cities, it's good idea to just like give it a few and see if the CPU efficiency is good. There's also this kind of like, like, if you know that your program does support multiple CPUs, it's also a good idea to make certain that the program if in the if in the program, there's some sort of like variable or something like how many processors to use like in in math lab, you might have like, what is the size of this parallel pool that create or whatever, like some sort of number that describes how many processors you want to use. You want to make certain that that number matches the CPUs you're asking. Because otherwise, you might end up in a situation where you launch your program launches more CPUs than it actually has access to. So so your program tries to use, let's say 20 CPUs, but it only has access to, let's say one. And then there's like 20 20 processors fighting for the one CPU. So basically, you have like, you try to cook 20 pots of pasta on one stove. And of course, like, it's going to be like, hell, you're not going to boil any of the water. Like if you have to like cook every pot for a second, and then move another pot in there, and you have to constantly swap which pot you want to put into the stove into the burner. Yeah, so it's it's going to be like a mess. So so you always want to make certain that how many burners you basically request. So in this case, you request two or one. You always want to make certain that your program puts as many like pots to those burners. So you always have like the system utilized. And also you have don't have it overutilized. So basically, like it can go wrong both ways. If your code doesn't support parallelism, then it might not use any more CPUs. And if it supports it but doesn't know about slurm and how slurm tries to tell a program, how many CPUs are available, then it might say, Oh, I'm here on a computer with 20 processors, but it only has assigned been assigned four of them. And but try to use 20. So so many things that go wrong. Yeah, but it's usually a good idea to just test and use the SF. Like the main thing is like you if you know how to do division, it's quite simple. So if you if it like launch a job, and you let it run for some time with one CPU, like you launch some job with one CPU and you get some sort of like runtime. If you increase the number of processors, you expect like in the perfect world, the amount of time used to like the amount of time required for the job to complete if you increase the number of processors is the like the time with one CPU divided by the number of processors. So you should like, if you just divide the number, the time that it took to run with one processor with the number of processors that you're now running with, you should expect like to get. Yeah, you expect like the time to be divided. So so if if you see some discrepancy, you probably know that okay, it's not working as intended. Like if there's some sort of like, like, okay, suddenly, like, the times don't match, like I increased the number of processors by two, but the time didn't drop at all, then you know that okay, like, like it didn't work. Yeah. So okay. So yeah, that's about all that we can say about, like, there's all kinds of talk in the in the documentation about how to do, like, how about these multi process jobs, but like, it depends so much on the program, so that we can't get generally use a general instructions, but but then yeah, if it's if it doesn't say MPI, then it most likely will use the other other data. The MPI is then a lot more complicated because like, but but usually it's it's it's complicated on the surface level, because usually, like, you don't compile your own MPI programs, you use MPI programs that other people have provided. So what MPI MPI is complicated because it creates this kind of like a communication between it creates this kind of a communication between multiple different nodes. So so and for that to work, it needs to know all about like system libraries, network libraries, it needs to like do so that you can get like information from across the nodes fast, like you can have a lot of communication. So if you think about like, traditional MPI program would be like, let's say you have a, you have some sort of like a finite difference method, or you have, let's say you calculate a grid, you have a grid of, let's say, you have the weather data that this describes, like a place or something. And then you have like a grid that describes the place, describes, let's say, over Finland or something like that. And the each grid point at some point in space. And each for each grid point, you have one MPI worker that calculates or may for few grid points, you have an MPI worker that calculates what happened in that grid point. And then all of those have to communicate with their neighbors. So it's a huge amount of communication usually. And that's why it needs these special, special libraries. But usually MPI programs, they, they, they usually work that you load this MPI module, which is provided by the system administrator, because that MPI module needs to be like very, it needs to work. And usually, there's only few versions that that are like actually tested that actually work. And then you compile your program against that version.  If your program is provided by the systems administrators, and it uses these MPI programs, you should use those MPI libraries that it provides, because like, they, if they're, if the libraries don't work together, then nothing works. So you should utilize it. But it's in the case of the MPI programs. If you reach out, go to the Hello World example there. Up above, I guess. Yeah, it's up above. Okay, here. Yeah, over here. Like, typically, what you would do is that you load some compiler. So in this case, in Alto, you would load this GCC compiler and this MPI library. In other sites, the version numbers might be different. The model names might be different. But usually, you load some compiler and some version of MPI. And then you compile your code. And if you want to reach out, show the, the Slurm script. Here we go. Yes, in the Slurm script, you typically tell the number of tasks. So, so instead of the number of CPUs, we are talking about MPI tasks. And this is because like the networking and all of the jazz. So if you're working with MPI programs, you specify this number of tasks. And if you're not, then, well, there's, you're, you're working with the other, other paradigm. There's also lots of like in this documentation, there's how to, like, if you're going to do MPI programs, if you're going to do these large scale MPI programs, this documentation here, how to spread the workers evenly, how to, how to like optimize, like how to choose the number of workers and so forth, complicated stuff. But it's, it's not something that most of the users will use nowadays. Like the HPC used to be that everybody was just doing MPI. But now, stuff has changed a lot in the last 20 years. And there's much more multi processing and much more data parallelism, so much more aggregate jobs. So those are the, like, the ones that you probably, like, if you're not in physics, you're most likely to do the other stuff, like, like the physics people, like you're stuck with the MPI programs, because the problems are usually so big that they need the MPI to solve that. Yeah. Okay, so we've got 10 minutes left. And did we already say that we didn't plan on doing dedicated exercises here? I guess that should be obvious by now. Should we do some demos or something? Like some exercises as demos or? Yeah, maybe we should do like the exercise one as demo. So if you scroll down to exercise one, like, because like these, these will show the concept, like in detail. So Yeah, okay. So let's see. Here we are. So I'm running s run CPUs per task equals four. So I'm telling, I guess there's one task and four CPUs. And then I run host name, which tells me what computer it's running on. So which, which of the, the type of paradigms is this? This is the multiprocessing one? Yes, yes. So in this case, like what we are just asking is that similarly to the, like the serial job, where we asked for memory resources, we asked for time resources. Now we're just asking for CPU resources. So just, just saying to the slurm that okay, like, whenever I get the, the kitchen I want to be in, I would like there to be four burners, like four burners available for me, could you make it possible? And then slurm says that yeah, sure, like I can I can figure you a place to work. And here are the four burners. But when we are running now the hostname command, of course, the hostname command doesn't care about the force for CPUs. So but, but in theory, if they would be a program here, that yeah, it could use them. Yeah, okay. So now if we try the number of tasks. And tasks equals four. So this is the MPI paradigm. Yes, I guess. So it's waiting. Yeah. So now that we launched this, we asked it to provide us for MPI workers. So you see that now the output is like quadrupled. So we get four times the output. So this because the hostname command doesn't understand anything about MPI. So what happens is that it duplicates itself. And like, in different nodes, we get all in this case, the same node, but in different places, we get four CPUs. But we have like all workers that all things four times. Yeah. So basically, now we are asking for like, we want four cooks, but we didn't ask if they all speak the same language. So so basically, we asked for like, can we get four cooks? And one one speaks Italian, one was Finnish, one speaks Polish, and one speaks Indian. And and like, none of them know how to communicate with each other. Is it like, they're not being told to work with other people? Because I think normally, yeah, yeah, like, like, they're just, yeah, like, they're not told there's even anyone else going on in this kitchen. So you're giving everyone the same recipe, and they all do it independently, because they weren't told, here's your leader, and the leader will tell you which part to do, or something like that. Yeah. Yes. So in this, like, if you, if your code doesn't use MPI, and you try to use this end task, what you have, what happens is exactly what happens here, that you launch the same program multiple times. And in those case, like you in best case, one of them finishes and three of them crash, like here. And in the worst case, they all try to like write same output file and, and like they mess up your data and stuff like that. So you don't want to do this, like, if your code doesn't use MPI. So let's try the number of nodes. There's also this option. So for big, big MPI jobs, you might want to do multiple nodes and spread stuff across multiple nodes. Does end tasks automatically take multiple nodes? If you have multiple? If you have so many? I think the default is that if you specify my number of nodes, you get one CPU, you get the number of tasks will automatically get multiplied to the number of nodes. But I'm not certain. I'm not completely certain. Okay. But like, like this, this brings to mind, like, if you don't know what the program is doing, like, usually it's, it's like, like, don't trust the defaults try to like, actually set the values that you want it to use. So in this case, we would get like, four different nodes that are tasks in four different nodes. So, but yeah, so, so the main thing is that like, you know, what kind of parallelism your code supports, if it doesn't support it, then a tough luck, then it's better to use the embarrassingly parallel thing. If you want to code your parallel code yourself. It's good idea to check out like, many of these, like you can check MPI, you can check open MP, you can check, like, there's huge bunch of different libraries and systems that provide parallelization. But but usually it's it's better to use, like, ready made products that somebody has already written because like, in lots of, if you don't, if it's not optimized, then lots of time can be used in like, don't doing nothing, basically. So it's good idea to because like, the the there's always in every program, there's going to be time that is serial time that cannot be parallelized in it's like, it's, it's provable by mathematics.  So it's good idea to check like, what is possible and what is not. And usually the embarrassingly parallel is the best way to parallelize stuff. Maybe we should make a flowchart of the best way to do things. But anyway, yeah, if you want, yeah, if you quickly want to switch to my screen, I will quickly show this, like I, I don't know if this helps, maybe it helps somebody, maybe I'll make a graph out of this to the documentation. So basically, this, this is kind of like a hierarchical structure of what the jobs can be. So typically, you can have like an array job, you can either have an array job or not. And it basically just copy paste everything underneath it. Like if you, it just sets the array index and then everything underneath this is as it is. Then each job can have its own requirements in these espatch comments. So when we write this serial job, you can have this espatch comments. And each job step that we run with s run, inhering the requirements from the main main job. And each job step can have multiple tasks, like this MPI tasks, but only for the MPI jobs, otherwise, the top number of tasks will be one. And each of these tasks can have one or more CPUs allocated for it. So it's this complicated mess. But like, you don't have to think about it too hard. The easiest thing to like think about is like, does my program say something about number of workers? And if it does, then just try using my multiple CPs. And if it doesn't, then yeah, doesn't matter. Yeah. So it's We have any questions in the company? Nothing? Let's check. Yeah. My hands are getting a bit full here. So what comes next is a talk by CSC. So when you need even more resources than there are at Alto, then this is a good option. And it's not just computing, there's resources for data, secure data, many different things. And I think we'll hear about various of these. And then after that, we come back and we talk about GPUs. So the GPU part is not about writing your own GPU code because most people don't do that, but about running things on GPUs. And that turns out to be quite important for many people these days. So with that, should we go to a break and we'll be back at zero zero? Yeah. Okay. See you all then.


Unsupervised learning may sound like a fancy way of saying, let the kids learn on their own, not to touch the hot plate. But actually, it is a pattern finding technique for mining inspiration out of your data. It has nothing to do with machines running around on their own without adult supervision. Instead, it's all about similarity, running algorithms that put like with like. It's an algorithmic way of enforcing birds of a feather should flock together. The secret is that behind the scenes in unsupervised learning, there is actually human supervision. Humans will look at the results and ask, is this good? Am I finding it interesting? If not, they're gonna fiddle some settings or they're gonna hit run again. So even though there are no labels put in in the beginning, the labels that come out are labels like group one, group two, group three, group four. But if you, the user, the analyst, the data scientist don't like those groupings or you're not inspired by them, what you'll do is you'll say, try it again, try it again, try it again. That act, try it again or try it again another way or re-randomize or try different settings, that part is the part where the human gets to supervise the system a bit. So there's not really such a thing as completely unsupervised. And because we impose what we think is good, what we think is valuable on there and those notions of good and valuable is preferences that we have are driven by our past experiences. Our biases get into unsupervised learning results just like they get into supervised learning results. So don't think that unsupervised learning removes human bias. You, the user, you are putting your own tastes on it by asking, do I feel inspired or do I not? Do I wanna try again? Do I wanna re-run? What inspiration am I getting from these data?