By order of the Overseer Council, certain parts of this file are subject to level 4 or higher classification. Research in the SCP-1730 is currently ongoing. Individuals involved in research may be subjected to the effects of known or unknown carnitohazards. Information on these hazards is on a need-to-know basis only. Individuals attempting to subvert these classification measures will be subjected to immediate termination by a Class 8 Red Kill Anomalous Mimetic Hazard. Item number SCP-1730 Object Class Euclid Special Containment Procedures A circular perimeter has been established 2 km from SCP-1730, and a quarantine zone has been established 1 km from SCP-1730. Personnel who are to enter SCP-1730 must first undergo Class 7 Hazardous Contact Preparation Measures, including the application of a modified Maxwell-Harton Hazardous Material Reinforced Air Tight Suit. The application of these protective measures may only take place at the Provisional Site-23 Quarantine Main Gate. Individuals attempting to exit the quarantine area must first submit the thorough decontamination protocols as administered by the quarantine security staff. Individuals failing to meet the quarantine extraction parameters are to be held for further decontamination, or in the event decontamination becomes unfeasible, termination. Containment Update Dangerous biological and carnitohazards entities have resulted in high casualties of security rescue teams. Mobile Task Force Zeta-9, mole rats, have been assigned to all current exploration efforts. Containment Update Due to the events detailed in Exploration Log 7, all future exploration of SCP-1730 have been suspended indefinitely, pending overseer approval. Description SCP-1730 is a large complex of structures 15 km northwest of the U.S.-Mexico border within Big Bend Ranch State Park that was discovered in June 5th. Due to the isolated nature of the complex and the low survival rate of individuals who come in contact with it, it is possible that SCP-1730 had been previously discovered but unreported. SCP-1730 bears identifying markings that contain documents to support the claim that SCP-1730 was at one point Foundation Site-13, originally located near Nome, Alaska. This conflict with current records would show that Site-13 with a project that, while intended to be constructed in Nome, was scrapped for the larger and more advanced Site-19 and ever completed. Flora located on site have been traced back to those native to the Alaskan region. How SCP-1730 came to be at its current location is unknown. SCP-1730 is in a severe state of disrepair and appears to have been left abandoned for an extended period of time. The Site Power Generator has continued to operate in a damaged state despite a number of fuel leaks and fires throughout the facility. This has resulted in intermittent power failures throughout the site hindering exploration and rescue efforts. The origin of SCP-1730 is unknown, as is the nature of many of the anomalous entities contained within. It is confirmed that the 2nd through 15th basement levels were utilized for entity containment, though the state of that containment has deteriorated significantly. Footnote 1 While records indicate the 4th were utilized for containment entities, it is uncertain how far down the facility actually extends. It is believed that a contingent of human survivors exists somewhere deep in the lower basement levels of the facility. Messages written in English have been discovered throughout the site consisting of warnings such as danger and death here and other messages such as not my body and bleed. A recurring message, what happened to Site-13, has been found in several different locations in the basements. Several logs of data have been collected by the remaining functional site terminals, the relevant data of which is contained in the addendums below. Worth noting is that inconsistencies exist between the logs and what has been determined through exploration, including the site layout, staff make-up, and contained anomalies. Addendum 1730.1 Recovered Log SiteLog1.log Team, Charlie Yukon, Assignment, Site-13 Recovery, Lead, CY-1 Begin Log We found it.  Blood looked funny too, too dark. It was running out of his hair, like through the follicles. His hair fell out right with it. Once it was over, the thing that crawled inside of him crawled back out with a buddy.  The other one crawls back inside Dailey and he stands up, turns around and starts coming at us. I can see that thing inside of him when he opens his mouth, so I pull a bullet in his face, then another. We emptied our magazines into him, he didn't get up after that. We're not going to be too much longer though. Found another one of those messages down here, you know. Just a matter of time before it starts. We strapped some C-4 to it and blew the wall, and I think it's pretty eligible at this point, but it doesn't matter. Jones already went quiet like the others. We shoved him down an elevator shaft earlier, didn't hear the body hit the ground. Think I just heard them start up Thresher. I wish we would have known about that sooner. Oh well. Addendum 1730.2 Recovered Automated Message R-E-C-M-E-S dot LOG The following message was recovered from SCP-1730's emergency warning system. Logs on file indicate that it was transmitted moments prior to a major electrical disturbance, and three minutes before an explosion within the site power relay. General notice, Site-13 has experienced a gross breach of containment systems. As breached containment during testing, on-site nuclear device is non-responsive. Thresher protocol has been activated. Life support systems online. Electrical systems offline. Fire control systems offline. Flood control systems offline. Reactor status critical. Euclid class containment status critical. Cater class containment status compromised. Item 1730.3 Exploration Log Transcripts Log 1.LOG Initial Exploration Video Log Transcript Date ██████ Exploration Team Mobile Task Force D-12 Budslingers Subject SCP-1730 Team Lead D-12 Cap Team Members D-12-1 D-12-2 D-12-3 D-12-4 D-12-5 Begin Log Recorders on, everyone check your mics. Check. Check. Check. Check. Check. And check makes five. Right command, you hear us clear? Roger that, Team Lead. Alright, keep weapons locked. No idea what we're gonna see in there. Yep, we're set. Let's move in. Those doors. Team moves into main SCP-1730 structure through front doors. Doors found to be unlocked. Keep your eyes open. Dark in here. Lights. Good call. Team switches on shoulder-mounted lights. Something written on the wall over here. Yeah, here too. What you got? Get below and don't look at the walls next to it. Little late for that. What about you two? What did we do? You see that command? Yes. Alright, let's move on out. Service elevator over there. Five. Check if it has power. Yep, this will work. Let's see how far it'll take us in. Team enters service elevator. Video indicates lit control panel with various four buttons. D-12 cap hits button labeled B-3. And away we go. Elevator descends briefly. Stops upon reaching the third basement level. Door opens to reveal a dark hallway. A single light is on at a bend in the hall, roughly 50 meters from the elevator. Okay, let's clear this level first. Then we can go from there. One and three. Take that hallway there. Myself and four can check the rooms in this hallway. And two and five stay here. Make sure our elevator sticks around. Team splits up. D-12-1 and D-12-3 moves towards the light at the end of the hallway. D-12 caps begin checking rooms to the left side of the hallway. D-12-4 checks the right side. Rooms are filthy. What is this? Yeah, I see it too. Is it mud? Feels like it. Some kind of sludge. Smells metallic. Pulls test tube from belt. I'll send this back up as I command. Let you guys poke around in it. Acknowledge. Try and keep out of it as much as you can until we can figure out what it is. Sure thing. We're at the end of this hallway. Another hallway here looks like there's some kind of barricade at the end.  Can you approach the barricade one? D-12-1 and D-12-3 approach the barricade. More of the sludge in this room, caked on the walls, found a body. Hang tight one. Don't move. D-12-CAP enters the room. A visible humanoid body is seen half submerged in the thick black material in the corner. The head and neck are not visible. Yep, any kind of identification. He's got a spot on his belt for a badge but is missing. Looks pulled off. Maybe to unlock a door somewhere? Maybe. Go ahead and proceed one. Aye. Cap. More bodies here. That sludge is all over the back of this barricade. Shit. That one moved. There's something else in this pile. Got a light on it. Moving your way, guys. Oh, there. Fuck. Gunshots. Report, guys. We're getting to you. Thing crawled out of one of their mouths. Some kind of snake, I think. A lot of teeth. Can't really tell what it is now. Look here. You hit that body. See that? Fuck. It's hollow. D-12-CAP and D-12-4 arrive at barricade. You seeing his command? Affirmative. Alright. Watch for that, then. I guess. Weapons hot. If they aren't already. Aye. Let's see if we can't get down the next level. Is that door unt… Yeah, I thought so. Let's just do that, then. D-12-CAP, D-12-1, D-12-3 and D-12-4 move back down hallway. Wait a second. Didn't this turn left earlier? Sure fuckin' did. Where's the elevator? 2-5, you read me? Silence. Here we go.  Shit. Command you read us. Sure do, Captain. You got a read on 2-5? Should be about 45 meters to your 12. Where's the wall here? Looks like it's always been here. Either we're hallucinating or the building is doing something fucky. Either way. Can you get a hold of either of them? A moment. Site command attempts to communicate with D-12-2 and D-12-5. Neither of them are responsive. No go.  Let's just find a way up and get out of here, then. D-12-T proceeds down hallway. Notable. Hallway is much longer than any on any recovered schematic of the site. Got something else on this door. What's that? Says silence. We're trying to check this. Is this a containment cell? That's just an office door. The whole floor looks just like offices. Alright, then. Get in there. D-12-1 attempts to open door. It's locked. I can't get it open. Knock the door down, then. You hear that? One. Two. It sounds like somebody's shushing. Three. D-12-1 kicks down door. Video records three frames of a naked human what appears to be fire burning out of its ears staring fearfully at the door. Fuck. This is an intense white light and the sound of searing meat. All camera lenses are damaged and become non-functional. All microphones except for that on D-12-3 stop working. What happened? Captain. D-12-T team. Site command attempts to communicate with D-12-CAP for an additional 30 seconds before realizing that D-12-3's mic is still operational. D-12-3, can you hear us? Static. D-12-3. Static and then the sound of slithering. D-12-3. A cry, then the sound of choking. This continues for 43 seconds and then the sound of liquid leaking, then pouring, accompanied by the sound of vomit. Large wet objects can be overheard hitting the floor. A dull, low approaching sound accompanies this. Mic cuts out suddenly. D-12-3. Shit.  Haste site command. Jesus Christ. What? D-12-2? Where are you right now? By the elevator. We assumed our radios had stopped working down here. We're just waiting for them to get back. The rest of the team is compromised. Hang on. We're trying to establish a link to your video. No need for that. It's probably just interference. Can you send the team down here to get us? Hang on. Video coming up. Don't. Got you. You. Mounted cameras on both individuals did not show the hallway they had been standing in, but what looks like a large utility room. Boilers are visible in the near distance, and a wall appears to have been caved in. D-12-2 appears to be hanging upside down, facing D-12-5, both of whom are stark white and unmoving.  A large object is seen moving quickly behind D-12-2, accompanied by the sound of slithering from many different sources. D-12-5 opens his eyes. Two frames later, the video and audio fee cuts out. No additional responses are picked up from the D-12 team. End Log. Log3.Log Initial Exploration Video Log Transcript Date ██████ Exploration Team Mobile Task Force Y-24 Gulliver's Travelers Subject SCP-1730 Team Lead Y-24 Cap Team Members Y-24-1, Y-24-2 Notes Initial exploration of the main site structure proved two dangers from an additional attempt without additional resources. The only remaining Mobile Task Force on hand was Mobile Task Force Y-24, a three-man team who was charged with entering the site power station and assessing the damage. Coming online. Video and audio feed for all three members come online simultaneously. Ahead of them is the entrance to the SCP-1730 power station. Can you hear us? Affirmative. Good. Anything else we should know. Thermal scans read one of the cores as being superheated. Might be on the verge of an explosion. Stay as far away from them as you can. You can use the micro drones if you need to. Don't worry about trying to get them back. Right. Okay. Good. Let's get on. Y-24 team enters power station. First room appears to be a security station. There is our first problem. Doors are locked. These are pretty solid too. Is that glass bulletproof? Check it. Loud thump. Guess that answers that. Command, are we cleared to use explosives in here? Negative. Structure is pretty weak all over. You'll risk caving yourself in.  There's no other way in. Hang on. Anybody on site with a level 4 clearance card? One that can override breach lockdowns? Dr. Edwards is with a team over at the containment bay. No, no. It would have to be somebody older. Edwards has only been around, like, what, ten years? Somebody who's had the clearance for a long time? Standby. Director Jameson is currently on assignment at Site-65. Yeah, that's three hours from here. We won't- No, you've got the right idea. Get Director Jameson on the phone, Command. Ask him what his clearance code was in. When was Site-19 built, 1960? Standby. Ten minutes past, extraneous logs removed. Alright, you ready? Go ahead. Well, I'll be damned. Hello, Researcher Jameson. Will you look at that? We'll send the Director your regards. Please do. Good work, one. Let's get in here. Team enters Power Station main concourse. Can you see the damaged core? No, they all look fine. Let's switch to the thermal lens. There it is. Are we missing something? That core looks fine. We need to get closer to it, guys. Right. Releasing Micro Drone, Command. Y-24 Cat releases Micro Drone. Drone approaches Power Station cores and begins to circle them. Twelve cores are accounted for, seven of them damaged beyond repair, three have not been brought up to power, and two are operating at full capacity. One of the two is a superheated core, which aside from its abnormal temperature shows no other sign of damage. It looked fine. Can you get closer to that, Captain? Sure. The Y-24 team approaches the superheated core. Temperature readings begin to rise as they grow closer. It's hot enough, anyways. What's this shit? It's really thick. Is that sludge? Some kind of waste? Try and avoid that, team.  Yeah, hang on. Two, grab one of… Yeah, you got it. Samples on the way, Command. Thanks. Be careful, guys. Try to get around to the other side of it. I'm over here. Nothing looks…  One camera shows no fewer than 10 human bodies bound to the side of the superheated core with wire. All of the bodies appear similarly to the bodies found by the D-12 team. Stark white, blood leaking from all orvices? Non-responsive. Something written underneath them. Is that blood? What happened to Site-13? These lines don't run up the main structure. See here? They're running below us. Any kind of identifier? Let me see. Yeah, they're all labeled. Body pit. They run straight into the ground over there. Looks like we're going below then, Command. You copy all that? We do. Just proceed to sample back as well. Going to get a report on that in just a few minutes. Alright, good. Let's get down there. There's a stairwell over here. Y-2014 approaches stairwell and begins to descend. Lighting is absent in the stairwell, and all team members switch on their shoulder lights. These doors are all hardlocked. Y-2014 descends to the bottom of the stairwell. The door there is open. This has been pried open. Looks like somebody was trying to get out, not in. Something else written on the wall here.  Heh, that's polite. Team enters the doorway. You smell that?  What is it? Whatever's on the other end of this hall, I imagine. Watch the blown radiator here, guys. Team, take note that we're losing video feed. Something's interfering with our signal here. Roger that, we- Audio feed cuts out. Positioning system stays active for a few more moments as Site Command attempts to reconnect with Y-2014. Intermittent communications are received for an additional 15 minutes. Some of these are human. That same. It's all over the inside.  Something crawled out. Look. Do you hear? We need to get- There's a light over there. Can you see it? Hello? Are you okay? Do you need help? We can. Audio cuts completely. Recovery efforts are halted. No communication is received from the Y-2014 for an additional 24 hours, after which the team is determined to be lost. A sample that was returned with the micro-drone revealed to be blood and power core residual runoff mixed with some kind of additional biological matter. Study into the substance is ongoing. After one week, Y-24-1's video feed becomes active again for 13 seconds. No audio is transmitted, and the video shows a group of humans standing around looking at a table. One of the humans turns to look at the camera and the video cuts. No additional communication is received from the team at any point afterwards. Log 6.log Initial Exploration Video Log Transcript Date ████ Exploration Team Mobile Access Drone Subject SCP-1730 Team Lead Not Available Team Members Not Available Notes While waiting for additional resources to arrive at SCP-1730, an unmanned ground-based drone was launched into the main site complex through the same door that the D-12 team had entered. The planned goal of the mission was to investigate lower floors and attempt to recover information relating to the origins of SCP-1730. Begin Log Drone approaches main office building and enters through front door. A moment is spent observing the writing on the walls in the interior lobby before moving across through the service elevator. Drone enters elevator and turns to floor selection. There are selections for five floors above the ground level and fifteen below. Drone moves to select B-15 level. Elevator begins to descend. After seven floors, elevator suddenly stops. After a few moments of time, it is determined that this is due to an intermittent power failure. Drone uses suitable utility to open the forward-facing elevator door. The open elevator shaft is visible, and the drone is unable to determine the depth of the shaft. Using its winch, the drone descends below the stopped elevator to the first available floor. After prying open the door, the drone swings into the opening and retracts the winch. A sign on the wall just inside the doorway indicated that this is the eighth basement level and that it is a Euclid-class containment wing. Lights on this floor remain dark. The drone is instructed to move down the main hallway and look for a suitable area to descend to the next floor. Drone moves toward the side hallway and is instructed to explore down it. It is noted that a number of messages are written on the walls, including don't look at the walls and kill the quiet ones. After inspecting a number of rooms and finding them to be only empty offices, the drone returns to the main hallway. Drone sees his movement upon seeing a large, vaguely humanoid entity standing near the end of the hallway. See the expiration file Drone139.jpg. This entity appears to glide slowly down the hallway, seemingly not noticing the drone. After it passes, the drone is instructed to follow the entity. Entity enters a maintenance closet near the end of the initial hallway. Drone observes this entity extends a long arm from underneath its outer layer and touches the floor. Upon further observation, the entity is noted to have picked up some of the thick, dark material previously identified as blood and power station runoff, with what is identified as its primary finger appendage. Entity then begins to make slow movements towards the hall behind it. This is obscured from the drone's view. The entity sees his movement and then slowly turns to leave the room. The drone is instructed to move towards the wall and take note of any changes. It is noted the entity left behind a number of unique symbols, such as ████████. The drone takes several flash photographs of these symbols and transmits them back to site command. Drone is then instructed to continue to follow the large entity, however the entity has disappeared from the hallway. It is noted the entity left no apparent footsteps, even in the thick material covering parts of the floors. Drone is instructed to continue on regardless. Drone reaches what appears to be a series of several containment cells. The first cell is open. A placard on the side of the doorway reads, Entity 324, Schedule Determination, December 13, 1975. The drone enters the doorway and observes a spacious containment cell. Thick rubber padding is all along the walls. The drone notices a human form in the corner of the room, covered in a thick, dark sludge. As the drone approaches the form, small sparks fire from his fingertips towards the drone. The drone takes several photographs and then leaves. The next three cells are all empty with no placards. The fourth cell is closed, and it is placard to smash. Drone is instructed to attempt to open the door with its cutting torch, after a few moments it is able to do so. The drone enters the room. In the corner of the room is the emaciated body of a human female, roughly aged at 34 years. The body shows no sign of life. A chain is seen around the neck, descending into the shirt. Notable is the lack of sludge within the cell, possible as a result of the inhabitant closing the door and locking it from the interior. The drone searches the corpse for an identification badge and finds one. The name reads, Jack Bright. Drone is then instructed to search the neck chain, but the chain is discovered to be broken. The drone then leaves the room. The drone traverses the short way until it finds the stairwell. The drone descends to the next floor. Assigned by the doorway reads, Fifth Floor. The drone turns to view the stairwell it had previously descended from, but finds it nonexistent. After some short discussion aside command, the drone is instructed to enter the doorway. The drone enters into a large, spacious office floor, lit by sunlight. Several terminals are nearby, though all of them have been destroyed. The drone approaches the least damaged terminal and attempts to power it on. The terminal does not power on, though whether this is due to a power outage or damage to the machine is unknown. The drone maneuvers across the room, papers litter the floor, and many look to have been burned or shredded. The drone reaches a terminal labeled, M. Hadley, which appears mostly undamaged and attempts to power it on. The terminal powers on, and the drone then attempts to connect with the computer. The computer is running the same foundation-based system as the current model, albeit a number of generations older. The drone is instructed to transmit every file it is capable of accessing to Site Command. The drone begins to do this. Note, at this point in the operation, Site Command lost contact with the drone. Several members of the operation team suddenly showed symptoms of some kind of anomalous influence, growing silent and beginning to burn from their ears. After the onset of symptoms, any sound will trigger what appeared to be a silent explosion that shook Site Command and destroyed most of its communicative equipment. It was later discovered that the only individuals influenced by this were those who had viewed the symbols created by the large entity in the basement storage closet. Further examination by Foundation Cognito Hazard Specialists and Screening Technology ascertains the symbols themselves were a sort of pyroclastic-cognito hazard. Any individual becoming aware of the symbols would inevitably succumb to the effects of the hazard, making any additional exploration of the site hazardous. The drone was left unattended for several days thereafter, though it did complete its task of transmitting the terminal contents. The contents of the search can be accessed in Addendum 1730.5. Attempts to reconnect with the drone was unsuccessful, and drone surveillance of the site from outside of the building showed that all the floors above ground level and the primary structure were entirely empty. The drone was not located. Log 7.Log Initial Exploration Video Log Transcript Date ██ Exploration Team Mobile Task Force Z-9 Mole Rats Subject SCP-1730 Team Lead Z-9 Cap Team Member Z-9-1 Z-9-2 Z-9-3 Z-9-4 Z-9-sub Notes Due to high casualties sustained by previous exploration attempts, it was decided that a team experiencing exploration of anomalous structures would be called into continual operations at SCP-1730. To that end, Mobile Task Force Z-9, Mole Rats, was assigned to SCP-1730. The team consisted of five explorative members and one support member who would stay at Site Command and monitor fluctuations of local reality. Begin Log We're online. Let us know when you've got a link support. Coming up now, I'm loading your displays with what should be a pretty accurate map of what you should see in there, but… don't bet on it, right? Like always, it's fully possible that there is a type green in there alongside the other nasties. Alright, Command, what's the worst of it? There is at least one Cognito Hazard's Entity writing Hazards on the walls. Your displays should be able to filter out any and all messages written on the walls, so we don't take any chances. As for the rest, it's a containment site. Awesome. There you have it, guys. Load up. Let's get in there. Yes, ma'am. The Z-9 team enters the main structure but search the upper floors first. As observed by the flying drones, the floors are empty. There is no sign of the previous exploration drone. We're clean here. How are we looking support? Holding steady, Captain. Nothing out of the ordinary. Tell Fordy he needs to adjust his channel frequency. I'm having trouble connecting to that module. Will do for… Check your frequency. You're falling out. The team descends the main level. After ascertaining the functionality of their Hazard blocking displays, the team moves towards a descending stairwell instead of the surface elevator. Going down now, starting to see some of that sludge, any idea where it comes from. Part of the mixture is power station runoff, but it's mostly blood and some other biological residue, like pus. As for where it comes from, your guess is as good as ours. Guess that's what we're here to find out. That's the one. This stuff doesn't stink like you'd think it would. Just smells like pennies. Tighten up, all. We're going into the dark. Team descends several levels until they reach the sixth basement level, marked as a euclid containment wing. Z-9 cap motions to enter the floor. Lots of bodies in here, Cap. I see them. Not all human, are they? Nope. They've all got that look to them, though, from the briefing, blood on her faces. Stay alert, guys. Copy that. Let's keep moving. Team moves forward for a short time, investigating the mostly empty floor. Suddenly a rumbling is heard. All team members stop and wait for the noise to end. There are the crash, and Z-9 force shouts. So what was that? Came from below you. Notice any structural damage? Sure fuckin' did. Four collapsed under Randall. He's down below us. I can see him. Four, you read me? Yeah, Cap. I'm gonna arrive when my leg is pretty fucked. I don't know if I can get up. Alright, stay there. We're gonna get down to you. Three, you stay here with Randall. One, two, move with me. Let's find a stairwell down. Captain, something fluctuating below you. You copy? Z-9 Cap does not respond. Site command also attempts to communicate with Z-9 team and fails to do so. Communications continue to be transmitted from the team. Where are they? Should be on their way. Any way you can get down there? Not without breaking my legs. You sure? I think I can hear something down there. I can't hear anything. It's probably just the pipes. No, it's definitely something… it's… fuck, Brett, it's slittering. There's something down here. Hang on, mate. Cap, you read me? Cap? Two? Anybody?   I can hear it. There's something off-screen.  Gunshot.  Don't shoot anything, Randall. You'll… Z-9-4 cries out. Z-9-3's camera observes what appears to be a black, leech-like creature, approximately the length and width of an adult human arm, moving slowly towards Z-9-4. Z-9-4 continues to fire wildly, causing Z-9-3 to run behind the opening and the door for cover. Suddenly, the gunfire stops and Z-9-3 looks back over the edge. Randall, Jesus fuck, I… The creature has now entered Z-9-4's open mouth and is moving slowly down its throat. Z-9-4's mic picks up muffled cries and a low grinding noise, like chewing. Z-9-3 aims his weapon at the creature and fires, missing it when Z-9-4 twitches. Z-9-3 fires again, striking Z-9-4 in the arm.   Permission to fire on four.  Please. Z-9-3 raises weapon and fire at Z-4. There is another rumble and the ground beneath Z-9-3 gives way. Z-9-3 falls into the concrete below and is crushed by additional falling debris. Z-9-3's camera and microphone disconnect. Z-9-4's microphone continues to pick up Z-9-4 choking and vomiting for additional five minutes, after which Z-9-4 grows silent. Another leech creature emerges from its mouth and disappears. Z-9-4 stands and picks up Z-9-3's weapon. Z-9-4's camera disconnects. Note, at this point Z-19 was in full disconnect. Two members were consumed KIA, while the other three were not accounted for. After three hours of non-communication, Site Command contacted Overwatch Command to request a full stop to all explorative efforts in the SCP-1730. While waiting for a response, Z-9-1's microphone came back online. You didn't look, did you? Yeah, me neither, Cap. It was over there, against that wall. Is it not there anymore? I can get it open.  I think they're gone, yeah. But I don't want to wait around for… lower? What floor are we on right now, anyways? I thought they were only supposed to be 15. Fuck. Alright. Z-9-4's camera suddenly comes online, showing a massive room, dimly lit by many small flames. Further observation of the footage shows the small flames all originate from the ears of many humanoids, standing quietly around the walls. In the center pit is a large creature that appears to be covered in many smaller creatures. It is barely distinguishable in the low lighting. Several large pipes over the creature have been cut and are draining into the center of the room. The camera cuts out. What happened to Site-13? This is like the fifth time.  How am… Right. Wait. Yeah, I do too. It's coming from over there.  Fuck. Look. Open that door. Z-9-1 is silent. No, I… Shhh. Stay quiet. Need to get back upstairs. Hey, who's that? Z-9-1's mic disconnects. Z-9-Cab is standing in a very tall room, looking at some kind of large and intricate machine. She approaches the machine slowly before settling over some kind of input console with a backlit screen. Z-9-Cab wipes dust off of a label just above the screen. The word Thresher is clearly visible. Z-9-Cab's hands hover over the keyboard to console. Another distant sound can be heard over the microphone, later identified as footsteps. Z-9-Cab turns quickly to face the darkness behind her. As she turns, her shoulder-mounted light strikes something on the machine behind her and goes out. The footsteps grow closer. Z-9-Cab begins to breathe heavily and starts running through the dark.  Get… Z-9-Cab's camera disconnects. No additional transmissions are received from the Z-19. Addendum 1730.4 Recovered data from Power Station Terminal Thresher.log Dr. Hadley, as you can see, the power output to the Thresher device has been adjusted to your specifications. At your command, the reactors will surge to the full 55GW required to activate the device. Like I mentioned in our previous correspondence, the reactors will likely not survive this kind of power surge. The core dedicated to the body pit might, given its reinforced construction, but there will likely be significant damage to all the rest. Additionally, and you'll forgive me for speaking out of place since I'm not assigned to the Thresher device, but the device is still wildly unstable. The tests have been encouraging on smaller subjects and it might someday be an applicable piece of technology, but at this moment it is only considered a measure for very final attempts. Utilization of the device could make local reality unstable here, as well as wherever the device ends up. In other words, I hope you know what you're doing. Best of luck, Engineer-242. Addendum 1730.5 Collected Datalogs comlog1.log Dear Dr. Hadley, 340, we have received your communication and thank you for taking the time to contact us. We have considered your request, but at this time we cannot approve any transfers. If you are at Site-13, you are there because of your superb level of professionalism and aptitude in your profession and we cannot afford to have you anywhere else. You may speak to your site pharmacist about an amnestic regimen if you like, but we cannot allow you to transfer from Site-13. As for your concerns about Director Emerson's mortuary protocol, we understand your complaints. However, you must understand that anomalies, especially those classified as humanoid, are not human beings. Human beings fall into a very specific category of non-anomalous life forms. These anomalies may appear to be human, but are simply humanoid. As such, they are not entitled to the rights and privileges afforded to human beings by the ethics community. Our job is researchers to identify where anomalies come from, and then to identify how to best utilize those anomalies for the benefit of mankind. We are protectors, and we cannot protect unless we know everything there is to know about the threat at hand. Once we have learned what we can learn, we neutralize the threat. If you have any other questions, please do not hesitate to contact our offices. S.C.P. Foundation Ethics Committee Chair Global Occult Coalition Ethics Board Head 3-4-2-1-testlog.log Testlog Entity 3-4-2-1 Administrator Dr. 1-3-4-3 Test Purpose To identify Class-8 Entity's ability to bend reality while exposed to dangerous conditions and a Scranton-Molius inhibitor device Use of SCP-█████ to reanimate Entity between tests Test 1 Exposure to Temperature Negative 35°C Result Entity loses energy, becomes less hostile Extended exposure results in low external temperature and decay of skin layer Entity expires after 1 hour of sustained exposure Test 2 Exposure to Temperature 150°C Result Entity quickly succumbs to heat stroke Body shows sign of burning across all surfaces Organ damage is a result of extreme temperature Entity unable to change reality to save itself Test 5 Submerge in Water Result Data not found Notes, water seems to interfere with Scranton-Molius device Test 13 Exposure to Electricity Result Entity unable to save itself Body no longer salvageable Entity moved to body pit for incineration 129-com-1.log To Engineer-242, from Engineer-129 Subject, Control of Hazardous Toxins and Reactor Core We're having some trouble controlling the waste back up in the pit. The runoff is supposed to be piped off-site, but it keeps getting sucked back up the air intake into the reactor.  Either we shut off the reactor long enough to go down there and clean it up by hand, or we're going to have a pretty serious issue here in a while. Termination-log-1.log Data not found Summary of events Entity showed unwillingness to submit the further testing, and as such, was swiftly terminated by a wave of electrocution. Entity moved to body pit for incineration. Noting here that additional orders have come in from Director Emerson requesting a full scale termination of the entire humanoid wing. Those will be processed at your convenience, and we can begin to empty out those floors. Sincerely, Dr. 790 UnknownLog3.log has shown some tenacity, but will soon break under the mental pressure applied to it by the orators. This is not uncommon, many entities arriving for their initial inspection will resist exposure to treatment in some way, but it cannot be sustained for the duration of their time here. Entity does have a particularly interesting effect on ██████, which leads me to believe that we could repurpose that aspect of the entity by removing the face, neck, upper chest area and arms, and applying it to a Mark-12 using the ██████. I will send this notice to Dr. 874 Post-Haste and move forward with this project. Sincerely, Dr. 720 UnknownLog12.log To Dr. Hadley from Engineer-242 They took your leech boy down to the pit today, I made sure to alter his termination record accordingly, and made sure the output is still blocked up. I don't know what you've got planned for him, but that pit is pretty noxious now. It's not going to be good.  If you want to properly dehumanize your researchers, you put them in cubicles. The numbers were a joke from the beginning. If you're reading this, then you're left with a decision. What did you think was going to happen? Throwing the bodies of anomalies into that pit. Did you think that their being alive made them anomalous? Hell, being alive is the least anomalous part of our humanity. I thought you might have seen that, but then, things have changed. The containment breach was my fault, I won't lie to you. In my research, I had the pleasure of analyzing a young boy, his name was Elijah. He subsisted only on blood, and he could siphon it through others with his mouth, right through their skin. Like a leech, he had no mental capacity beyond two years, and yet he deserved the same chance to live as the rest of us. He did not choose to be the way he was.  So I modified his record. The fires of your pit won't have incinerated him, just agitated him, and that sludge has been building up. I'm glad you care to get it cleaned up. I'm sure you're glad too, it's pretty awful down there. Anyway, your decision. The containment breach was inevitable, and whether it was something that crawled out of the pit that did it, or my hand on a button makes no difference. You have a choice to make.  Either way, our world will be rid of you and your filth, and will be better for it. This is your death camp, Elliot. You made your bed, and now you get to die in it. Sincerely, haily. P.S. I don't know if you even remember when this picture was taken, but I'm sure you'll recognize your own face. Amazing how much can change in just a few years, isn't it? All because you were chasing a promotion. Incredible. I hope it was worth it.  I've got a nice worn spot for him to get set up when he arrives. You've made sure there will be plenty of blood for him.


Hey everyone, welcome to this week's video update today's Friday, April 17th Hope everybody had a great week of trading this week Before we jump into the alerts talk about who got caught being hot this week goes to Kelvin Q, you know, I think a lot of people get into trading and With the mindset of it's easy I mean all you got to do is push a button and if you hit it right you can make money and so they come in with the mindset of really easy money and As all and I know I'm preaching to the choir here I know all of you know this but for for newer members who who come in thinking it's easy That's obviously not the case right anything worth Doing anything that is potentially as profitable as this can be for you. It takes hard work. It takes discipline takes experience Kelvin's come in and he's just he keeps asking really great questions in the community Which helps other new traders as well so I could tell he's putting in the work and You know really trying to understand and I always appreciate people who come in with that type of Mentality so keep up the heat Kelvin. You got caught being hot. Let's go to the alerts a little bit light on the alerts this week Just you know kind of letting some of our positions work for us But let's start with the first trade of the week and IWM didn't rolling adjusting trade This one was down to four days to expiration so we rolled it out skipped over may just went out to June to give it a little bit more duration and That's one of our short Delta trade. So let's look at IWM Right here So we've got two different pieces here. This is the one that we just rolled out to June and Widen this out a little bit for you. You see price is pretty close to where we put it on so not much movement Well some movement, but it ends up right now kind of back where we put it on and then this one is just right outside the range So again holding both of these for that short Delta exposure if we ever get it down move in the market again It's kind of baffling this this raging rip higher in the market Next trade rolling adjusting trade in NG so a natty gas we had a short strangle We rolled this we adjusted our calls from 192 to 190 had a conversation in the community about this Why did we why did we roll? Roll those calls that way kept the puts the same the reason the only reason really was because there was no 1.92 strike out in the 43 day cycle So we just had to take the closest thing to it still did it for an overall credit See we bought this one back for that sold for that the net net credit So that's what we're looking for when we roll strangles and so now we've got a 1.90 straddle and Let's take a look at that. Natty gas is up a little over 3% today. So price is pretty well dead centered We've made back about 360 bucks this week since we did that roll just waiting for some more time to pass working our way back To some profits in Natty Next trade opening adjusting trade in ES So we added a long put vertical in ES just to add some more short delta exposure and so we've got two sets now We take a look at ES One of which and we did these in in just slightly different expiration cycles to kind of keep them track This this one is is way out of range So we need some some down movement to get back in and then this one is the one We just put on and price is pretty close to where we put it on so Remember as we've been just rallying higher You know, we've just been consists, you know consistently slowly methodically adding in some additional short delta I've talked about in a couple of the weekly trade hacker updates that we're definitely not overly short In fact, I wouldn't mind even getting a decent amount more short delta on But we've just been kind of layering in as this thing's been going up And we're about one-to-one on our on our short delta versus our theta. So certainly not overly short You know days like today when Apparently gild came out with a with good news about a vaccination for the coronavirus had a big up move overnight S&Ps were up over 90 overnight Up about 41 now.  And so that's part of what we did here with this ES Next trade closing adjusting trade in CL. So we had two different short strangles on in CL We closed out one set booked over 50% of max profit on that piece Obviously still working our way back after that massive move that we had to battle in oil you know after the Saudi-Russian deal fell apart and What's interesting is is apparently the you know the 23 country OPEC agreements in place and oil production has Been reduced, but yet oil is still going down. So go figure We'll see what happens. I do want to add again to this. So let's look at our current piece in oil It's this inverted strangle that we've got prices hanging out right here in the lower end of our range So we definitely could use a spike higher in oil to benefit that But I will be looking to add another centered short strangle around the current price and we'll do that in oops We'll do that in this one's got 27 days to expiration So we'll do it out in the July cycle and next week that should be under 60 days if I remember, right? And Come on come on. Yeah 61 so next week that'll be under 60 days And so we'll look to add next week in oil Next trade closing adjusting trade in GC. So we had a we had two pieces on we had a full iron condor Which this is what this alerts about we booked over 40% of max on that piece of the trade And then we're still holding our call vertical from our previous iron condor. So if we take a look at that Golds come down nicely down 2% today. So almost back into range hanging out right here If we get back into this range here, we'll we'll take that off and end up booking a winner on that piece as well In the meantime, we're gonna add to this again next week So we'll add another iron condor centered around the current price wherever that may be early next week and This this current piece right here. It's only got 10 days expiration. So we'll be closing that out next week Regardless of it's a winner or a loser Don't really have a major directional bias and goals. I don't plan on rolling that. So we'll just close that out We'll add another iron condor in Next trade opening trade Did a a new weekly double calendar? So Okay, so had some questions about this and I want to I whenever this a couple weeks ago in the weekly video And I'll kind of reiterate my thoughts and So here's the deal whenever we Whenever we put these on You know, we've we've been pretty consistent about staying in kind of that six to eight days to expiration in that front week But there's been some questions about why are we why are we using such short duration between the front and the back weeks? Only three days Whereas in the course we talked about, you know selling the seven in the front week and doing, you know Buying closer to the 21 in the back week in in I think in normal market conditions, whatever Take that how you want in normal market conditions That that's a that's going to be a very viable way to do it What we've found is that in periods of extreme volatility You can get a little bit more bang for the buck by using shorter duration Between the front and the back week and here's what we're looking at So we you know, we you know in an ideal world we want to Sell the front week which has higher volatility So in this case the seven days have 35 point two one currently and the back that we're buying has lower Volatility so we're selling the options with higher IV. We're buying the back week with lower IV and this this works You know, if you look down the line, you don't get it really a situation at any point I mean this one is a little bit higher than this one You know, but everything kind of evens out after that and so We're just trying to take a take advantage of the difference in the high versus low In the front versus back and so that's why we're why we're doing that and that does a couple things one if we were to Sell the seven and buy the 21 a your buying power Requirement is going to be Significantly higher, you know, I mean it's gonna be three four five six seven seven thousand dollars a contract I can't remember what it would have been on this but Whereas this one, I mean, we're talking about, you know under a thousand bucks to enter this trade I think we put this on for nine ninety five or something like that And so that's part of the reason The other reason with high implied volatility. We're able to widen out these strikes and we're talking about the two 2690 and the 2860 when implied volatility is high you can make this wider get a higher probability of profit and still a really good You know profit potential especially based on the amount of capital that you're using so that's the that's that's the rationale for why we're doing this when we are you know when implied volatility changes when when implied volatility Financials between the different weeks is doing what it's doing. You've got to adapt And that that's what we're doing here. So I know, you know, some people kind of get frustrated They're like well, you're not following what you said in the course. Well, yeah, but this is real life trading I mean, we're trying to set the criteria in the course as a good of a foundation as we can and give you a basis to work on But but there's always gonna be you know situations where one one way works a little bit better So don't get caught up in in that too much Kind of watch what I do not what I say kind of thing. I guess I Mean we you know in the courses we want to be as we want to follow that as exact as as possible Don't get me wrong But just keep in mind that trading changes markets change environments change Volatility changes all that stuff. So things are things are gonna change and well We're actually gonna be going back through and updating a lot of our courses because a the other thing is we continue to learn Right. I mean, I don't I've never been the type of person says I know everything and so I continue to learn stuff about trading every single day A lot of that comes from you all in the community sharing ideas I mean, you know Tim wise started trading his version of the double diagonal and that just Sparked a little bit of ideas that that I had and I started messing around again and just just looking at different probabilities and and different strategies around on that same basis and you just you find Little nuances and little things that can really make a big difference that can create a little bit more edge Theoretically in what you're doing and so, you know, while the courses are recorded and they're static We will be updating those to kind of You know define what we're doing, you know, the other thing is on rolling verticals or placing long put verticals or long call verticals specifically, you know, we've you know based on from what we talked about in the course as far as our delta selection versus Sometimes what we do now setting it up for a specific probability of profit I mean, there's a little bit of variance there, too But don't again don't get caught up in details like that, you know, we wanted we do want to stay mechanical We do want to have a set of mechanics, but you also have to be flexible from a perspective of what's going on in the market and in kind of what you're trying to accomplish with that specific strategy and What other positions you have in your account? So, you know, we do manage each trade individually, but we also manage them in the perspective of the rest of our portfolio So there's a lot of little nuances that we're you know We can't just teach in a video course that that also come through these alerts and through these update videos and and on and on So hopefully that helps give you a little bit of perspective on what we're doing there It's been just an awesome strategy here in this environment. So We'll keep doing them as long as there is the opportunity Next rolling just in trade in Apple So we rolled our long put vertical and Apple got down to one day to expiration rolled it out to June When I would and skipped over May give a little bit more duration because we already going to be holding this for that short Delta Apple one of the stocks actually down big today down almost three percent, which is nice because we're shorted If we take a look at a chart You can see You can see this little nice little down move we're having today where it's been pretty strong For the last couple weeks. So good relief in Apple Let's see next trade closing trade in SPY. Okay, so we had a another weekly double calendar did this one in spy You know, I got some clothes, you know, what's what's the difference? Why do you why spy? Why not SPX did 10 contracts? You could have done one in SPX Just trying to accommodate more members really I mean you could have done either I Did set it up in both and for whatever reason the pricing just looked a little bit better in SPY at the time that we put it on In the the other thing from an accommodating members perspective, you know You know some members not all not everybody can do SPX, you know It's a big contract and so doing it in SPY sometimes just gives you an idea of which strikes to choose and you can do a You know a fraction of that you can do one contract or two or five or ten or you know, whatever you want So but you know if you see something come on anything I put out in SPX you can do an SPY Anything I put out in SPY you can do an SPX. So that's just a preference in your your money management and account style So an in account size so don't don't get too thrown off on that But anyway, so we booked this today We had it on yesterday. I was considering taking it off I think we're we're up like four fifty to five hundred dollars somewhere in there I could have taken it off for and the theta potential I talked about this in the community The theta potential looked really good as far as leaving it on And so we decided to keep it and then right after ours the whole Gilead announcement came out the market ripped higher I'm like, we're gonna get crushed tomorrow. We're gonna get the big move and the IV crush should have taken it off But actually this actually performed very well We ended up taking it off for like 750 bucks of profit. So good hold and good Good that that's the that's the weird thing about these double calendars is the you don't always know If the front week's gonna contract more the back week, especially when they're this close together. So performed well for us and Took that off booked a nice winner Rolling adjusting trade in DIA. So we rolled one set of our short call verticals This one was in May at 28 days rolled out to 63 to extend duration Also price was just so far out of range that I wanted to get back into range get this back into a positive theta situation So we adjusted the strikes as well So if we go to DIA So here's what we got here the 250 255 so pretty close to where we rolled it Just did that today and then our other piece is out of our range Scooch this in a little bit So we need some downside to get back into range on that one And then lastly did the same thing in QQQ had a had a May set of short call verticals rolled that out to June Adjusted our strikes This thing was just way out of range very little chance of getting back into range And I didn't want to just sit there and let the rest of the theta decay So we went ahead and rolled it and you can see we've made back about 50 bucks since today that we rolled and Then our other one out of range as well pretty similar to the DIA one Just needed nice move down to get back into range there. So those are all the alerts Let's take a look at for some of our other positions starting with 6e the euro now This one's at 21 days to expiration and so we certainly could have rolled it today But I'm just I'm hoping for just a little move higher over the weekend or you know early next week and Just you know book a little bit more before we roll Like I said, we've got 21 days So, you know that that's a that's another thing to you that 21 day mark is it's not like things get completely crazy between Day 21 and day 20, you know, it's right when you get down to 21 days That's when you want to start think about rolling. So anywhere from 15 to 21 is just fine And so just holding this see if we get a little bit of a bounce higher over the weekend and we'll roll this out to the next cycle. I Mentioned cl I mentioned. Yes, mention GC mention Natty Bonds bonds are actually down half percent now. They were they were kind of flat most of the day And they were actually down a lot last night. They've been they've been a little bit wild, but So we've got let's see It's this one here and this was way up here I'm so close to closing this out and taking that and then just kind of reducing our exposure Holding the other one and then it ripped back higher. So we're gonna we're gonna hold on and wait So that that one price is hanging out right here. We've made about 2200 since the roll and then this one here We're let's see Yeah, we're up about 760 since we did the roll So still we're obviously working our way back to profits in in in bonds, but I'd love to get a move lower Take one of these offs that we reduce our exposure and then you know, let some more theta work for us Let price move around and then add back in that would be the the ultimate goal here If we take a look at the chart of bonds You can see if we could get a little bit of follow-through from today, you know, I mean just a little bit We that would help us significantly on our bond position. So if that's where we're at there Wheat we've got an iron condor in wheat pretty centered here Just wait for some more time to pass. I mentioned Apple DE up big today up almost four and a half percent So we've got two different short call verticals that one's way out of range needs some downside to benefit that This one just barely out of range. So Again, just holding these for that short delta exposure DIA I mentioned that IWM I mentioned QQQ I mentioned SMH so we've got this adjusted short strangle in May prices hanging out right here and We will We'll look to roll this as we get closer to that 21 days. We're at 28 So we'll do this at the end of next week or early the following week SPX I mentioned SPY alright, so we still got a couple different things in SPY one of which is a bunker Price is hanging out right here. So it's gone up a little bit since we put this on This one's out in July. So this one's got decent amount of time 91 days So no no worries of continuing to hold that one for a while. And then we've also got an iron condor And prices hanging out right here in the upper end of the range So if we get a little bit of down movement, that'll bode well for that. I see Win big move up today. Disappointing up 6% not what we were looking for You know wins been on a nice little tear to the upside. So apparently they're Expecting people to get back to gambling pretty soon here But we've got this we've got this bunker trade on so on this June we're down to 63 days So early next week, we're gonna be taking this off You know the we want to take this off when we get down to about 60 days to expiration So we don't get caught in Death Valley down here And so we'll probably take a loss on that unless we get a you know big move over the weekend XBI we've got a short strangle on I've talked about this in Talked about it maybe last week, but we're obviously well over 50% of max profit This is an inverted strangle. So it's already been adjusted. So we're just working our way back to profits Pretty close in XBI This one has 28 days to expiration and next week will be under 60 days in the June cycle So next I'll just wait giving it a little bit more time in this cycle and then early next week we'll roll that out to June and And then we are pretty close to get back to even on that one XLI another bunker This one's not working out too well either. This is in June. So we'll take this small loss Early next week in that one as well And we might look to add, you know another we're gonna be taking these off So we'll be looking to add in something maybe we'll just add back in and in in XLI I won't add back in and win because there's earnings coming up. So Not really the best strategy to hold through earnings XLK another short Delta position. This is a long put vertical This is another one that's at a range to a point where you know very little chance of getting back So early next week will probably roll this one out to June as well Excuse me, and then lastly XRT now this one's a little bit different Now this one is in June as well So we're next week we're going to be in that 60 DTE range But look at the slope of the P&L line here, you know prices right here. So But I mean look at this It's not like this has even started to sag at all and so, you know, if we get a down move a implied volatility is gonna push This P&L line up and so I don't mind holding this a little bit longer than 60 days Maybe we'll take off one of them early next week But we will potentially hold this a little bit longer just because of the way that this is continuing to to slope So we can't really get hurt too much Obviously we can't get hurt much if it goes up from here and then if it goes down, you know It really starts to accelerate to the upside. So if we get a quick move lower in XRT, we still get some benefit out of that So we may hold that one a little bit longer But it'll be a candidate to add some new ones, too If we do close out just add some fresh ones on out in July or August. So that's the plan Those are all the alerts. Those are all the positions. Hope everybody has a fantastic weekend. Talk to you next week


Hello everyone. My name is Nikhil Gajam working as assistant professor in department of computer science and engineering in Valtran Institute of Technology, Solapur. In this session we will see a program for inserting a node at the beginning of a singly circular linked list. Learning outcomes at the end of this session student will be able to write a C program for inserting a new node at the beginning of a singly circular linked list. Now we will revise just in a minute that what is singly circular linked list. We all know that linked list is defined as a collection of nodes where each node contains two fields. First part is a data part and second part is a pointer which will hold the address of next node generally. But what is the difference between now singly linked list and singly circular linked list? In singly linked list a last node's next part which is a pointer which holds an address called as null or which stores a null indicating that this is the end of singly linked list. What is there in singly circular linked list? In singly circular linked list last node's next part which is a pointer part which holds the address of first node. That's why it becomes a circular one. So this is the major difference or big difference between singly linked list and singly circular linked list. So in singly circular linked list last node's next part holds the address of start variable. What is start? Start is a global variable generally we use to store the address of first node or start will always points to the first node. So this is a diagram difference between singly linked list and singly circular linked list. First diagram this is a singly linked list where three nodes are present in the linked list. Head always points to the first node. In some program we use a head or we use a start. In singly linked list last node's next part will always have a null value. In circular linked list or singly circular linked list last node's next part instead of storing null it will hold the address of head or it will hold the address of first node. It will become a circular one. This is a singly circular linked list. Next we will see an algorithm for inserting a new node at the beginning of a singly circular linked list. Now these are the steps. Step one is create the new node and store the values. So always whenever you insert a new node in the linked list program first task is to allocate the memory for new node and store whatever values you want to store in the new node first in the data part. Step two, if linked list is empty, you are checking whether a linked list is empty or not. If it is an empty set a value start or point a start to the new node because there is only one node and start will point to that new node and new nodes next will always have the address of first node. So new nodes next will point to itself only. Step three, if linked list is not empty or some nodes are already present in the singly circular linked list, in that case set a new nodes next to the start and set last nodes next part to the new node and set or update the value of start to the new node. So this is an algorithm for inserting a new node at the beginning of a singly circular linked list. We will see an example, a diagrammetical representation. Suppose I want to insert 10, 20, 30 in this sequence only. The start will have null value, next step is insert 10 as a new node in the singly circular linked list. So 10 will be inserted and 10s next will point to itself only. Next suppose I want to insert 20, so after 10, so 10, 20 will be inserted after 10 and 20's next part will hold the address of 10 which is a start and next I want to insert 30, so 30 will be inserted in the same procedure. Now I want to insert a new node 5 at the beginning of this singly circular linked list. So how to insert? First step is to allocate memory for new node, set the value 5 in the data part of this new node. Next step, new nodes next part will hold the address of start. This is the second step. Third step, traverse from start to the last node and set last nodes next part will point to the new node because you want to insert a new node at the beginning. And next last point is update the value of start, now start will point to the new node. So these are the four steps you have to follow whenever you want to insert a new node at the beginning of singly circular linked list. You can pause the video and you can answer what will be the value present in the next pointer of the last node if singly circular linked list contains only one node. So answer, if singly circular linked list contains only one node obviously that nodes next part will hold the address of itself. So answer for this question is address of same node. Now we will write a function for inserting a new node at the beginning of singly circular linked list. So this is online GDB where I have written some code already. So this is a structure node which contains two parts, data parts and next part. This is a start variable which is a global variable. This is an insert at beginning function which what we are implementing now this function. Display function will display the all the nodes which are present in singly circular linked list and this is your main. This is a do, while loop, main node event program there are only three functions. Insert at beginning we are implementing now. Display function is already there and ks3 for exit. So I will write insert at beginning function. This is insert at beginning. First whenever you want to insert a new node first task is to allocate memory for new node. So I will declare first variable two variables this is your struct node star new node and star temp. Temp is a temporary pointer used for traversing because you want to traverse from first node to last node. So I will allocate memory for new node. So this is new node equal to this is struct node star this is typecasting malloc function is used for allocating a memory dynamically this is struct node. This is size of structure node. So you have allocated memory and new node will point to that memory allocated. Now you are asking user that enter a value please enter value to be inserted. So this is scanf this is %d, address of new node arrow data. So you have stored the value in the data part. Now next part is to check whether link list is empty or not. Now to check if the start double equal to null meaning that singly circular link list is empty. In that case point start to the new node directly and new node arrow next will point to itself. So this is new node. If start double equal to null means singly circular link list is empty in that case whatever new node you have allocated that will be only singly circular link list otherwise so this is your else part else means there are some nodes which are already present in the singly circular link list and you want to insert a new node at the beginning. So in that case you traverse to the last node first so how to traverse temp equal to start. So this is while look this while temp arrow next this is not equal to start temp equal to temp arrow next. So temp will traverse till the last node when temp will point to the last node in that case it will come out of this while. So next part is joining of this last nodes with the new node. So how to join this temp arrow next last nodes next part will hold the address of new node new node arrow next so new node new nodes next part will hold the address of start and start will point to the new node. So this is a code so what I have done in insert at beginning function first I have declared two pointer variables first one is for new node second one is for traversing temp next one I have allocated memory for new node and I have stored the value inside a data part of that new node. Next task is to check whether singly circular linked list is empty or not. If it is an empty directly point start to the new node and new nodes next part will point to itself. Otherwise traverse temp from first node to the last node and then link last node with the first node new node and new node to the start like this. So temp arrow next means last nodes next will hold the address of new node new nodes next will hold the address of first node and change the value of start. I will execute this code ok this is printf case one for insert at beginning so I want to insert suppose 10 suppose I want to insert again a value I want to insert is 5 suppose and I will call display function. So it is printing now 5 and 10 10 is the first node I have inserted in the singly circular linked list it will be inserted at beginning next I have inserted 5 value so it will be inserted at beginning of singly circular linked list. So this is the code for singly circular linked list for function insert at beginning. Again I will move to the PPT. These are some of the references I have used for creating this video. Thank you.


Hello everybody! In this video, I'm going to show you how to view information on your computer in a Windows operating system and do it with standard system utilities for third-party programs. In our channel and blog, you will find solutions to any problem, from installing an operating system or configuring it to fixing possible bugs and errors or optimizing mobile gadgets. Our specialists will answer any questions you ask in your comments under the videos or articles. If you need to find the information on your computer's configuration, operating system, installed drivers and models you can support – for example, the name of your network interface card, graphics card or sound card, the version of BIOS or UFI, the version of DirectX your computer is using or the model of your motherboard – this video will be useful for you. So, let's begin. If you want to see basic information about your computer, open Settings -> System and then find the line about below. In the window that opens, have a look on the right to see three sections containing certain data. The first one shows how your PC is protected in real-time mode. The next section gives you basic information on the computer's configuration, processor model, the amount of system memory, product and device identifiers, and the system type – that is, if it is a 32-bit system or 64-bit system. The last section, Characterized Windows, shows the name, version, installation date of your operating system, as well as the build number. Below you will see three links. The first – Change Product Key or Upgrade your additional Windows. It lets you change the product key and read more about product activation. The two other lines let you read the Microsoft Service Agreement and the Microsoft Software License Terms. When you click on System, a window will appear containing system information. The System app dates back to Windows XP. It can show you more detailed data on the system and the hardware components. To open it, press the key shortcut to Windows Plus or type MSInfo32 in the window that appears. You will see more info, and it's more detailed. As you can see, it shows your operating system manufacturer, detailed information on the hardware configuration, BIOS version, motherboard model, system memory, and so on. If you expand the tabs on the left, you'll be able to use all functions of this utility. Well, probably all this data is most useful for software developers and system administrators only, but at the same time, it contains almost all the necessary information to know about your system. This is where you can see everything you need to know about the PC you're using. For example, in the Components section, expand Network and then click on Adapter to see comprehensive information on this device. Name and model of the network card, manufacturer name, driver version, current status, and all related settings applied at the moment. You can export all this data into a text file by clicking on a corresponding item. Then File, choose Export, select the folder and file name, then click Save. This option is very useful when you need to send your system data or information about the errors you are facing to another user or to a support help desk, or if you just want to save a copy of your system configuration and settings, just to be on the same side. Now, at any time, you can open this file and view all data and settings you are interested in. If your Windows fails to boot normally, you can use the command prompt to view the system information. And if your operating system fails to boot and you need to recover important data from the hard disk, watch a video in our channel on how to do it. Find the link in the description, as usual. Meanwhile, run the command prompt and go to the directory where this program is located. Type, then follow it with the command System Info. After the analysis, the utility will show the information on the system build number and version, processor, BIOS version, boot drive, and network. One way to get some information on your PC is by using Device Manager. It's the only tool to manage drivers for every device within the computer and handle the resources allocated for them, such as interrupt requests, DMH channels, memory areas, input and output ports. It also gives you more extra information. You can open it by right-clicking on the Start menu and selecting it from the list. Or by right-clicking on this PC and selecting Manage from the menu. In the window that opens, you can see all devices installed for this computer. Then go to any line you are interested in, for example, processors, and open it. You will see the window with properties of this hardware and the tab generally above containing general information. In the Driver tab, you will find information on the device driver and the options to update or roll back the driver, disable the device, or uninstall the device. Two other tabs show the details and events related to operation of this device. If you want to know, for example, the version of DirectX, which is a special set of ready-graphical elements, processors and functions that Windows operating system provides for use by external programs, the easiest way is to press the key shortcut Windows Plus R and type the command DXDIG. As a result, the DirectX diagnostic tool will start. In the first tab, you will see some data on your PC and the information on DirectX version. You will also see the data on the system, display, sound devices, and input devices. There are also lots of other utilities to give you more detailed info on your computer. One of those worth mentioning is AIDA64, and you will find the download link in the description as usual. This utility will help you to test and identify all devices connected to your PC, provide detailed information on the hardware and software components and much more. This is where you can see almost everything about your computer, from hardware to software details. When you open Computer Summary, the entire information will be shown. Computer type, operating system, computer name, motherboard name, video adapter, sound equipment, data storage devices, network, peripheral and input devices. For more details, open the tab you are interested in. In the Sensor tab, you can see the temperature of your processor, video adapter and hard disk, their voltage and power they are using. In the Benchmark test, you can check your system memory and processor. And that is all for now. Hit the Like button and subscribe to our channel. Leave comments to ask questions. Thank you for watching. Good luck.