Conducting an Experiment

Table of Contents

Section I > Introduction

ScD is one of the important departments within the Foundation, given its main duty of testing and researching anomalies. In a perfect world, research can be done easily and flawlessly. Sometimes it can be hard or challenging. That's why we exist—we can handle anything. Use this guide to help you on your ScD adventures!

Section II > Testing Incidents


In an experiment within Paragon Research Institute, it is almost impossible for something not to go wrong, so you need to know how to handle it. While testing, you might encounter the following potential problems: breaches, raids, combative mistakes, and the most common, Class-D non-compliance. Before you start testing, you must know how to handle all of these.


Class-D Non-Compliance 

If a Class-D is being non-compliant, you or your escort(s) must issue a strike each time they fail to comply. If they reach the third strike, you may ask for a replacement Class-D. If your escort(s) fail to issue strikes, you may report them for neglection of duties. Class-D that are under the effect of an incurable SCP are to be terminated when the test concludes. Replacement Class-D may be requested, but it is not advised. If the termination of the Class-D means a failed test, conclude your experiment and state as such in your report.


Riot 

In the event of a Class-D riot, researchers are to follow the instructions of Security/Mobile Task Force Personnel. You are expected to maintain a calm and collected composure during this period and to alert your escorting SD/MTF if they are unaware that such an event has occurred. 


Breach

If a breach occurs, you may continue your test as long as it's in another area of the site. If a breach is near you, or from your test, you must evacuate to a safe area and follow all orders given by Eta-9. If possible, bring your Class-D with you, otherwise let members of the Security Department/Mobile Task Forces handle them. If you are within the Clean Rooms, it is recommended you remain on the upper floor of the ScD laboratory, or make your way to the Breach Shelter in the floor below.


Note

If a test results in a breach and/or no test results are harvested, the report does not have to be logged.

Section III > Combative Escorts

Any test or interview that you perform must have a combative escort, even if the test does not involve the use of Class-D. If the test does involve the use of Class-D however, any researcher should know that the ratio for Class-D to SD is 3:1. That means that for every three Class-D, there should be one SD; for example, if you have 5 Class-D, then you would request 2 SD.


Regarding requests for tests within the CRs, there is a hierarchy regarding who can act as a combative escort. This hierarchy goes as follows: 

Base SD > MP > SRU > Lambda-7 with the one requesting having to wait 5-10 minutes before going to the next spot.


Clarification

Combative sub-divisions and/or task forces do not have to respond if they're already conducting another department duty. 


Notice

The CDC must be confirmed as stable and staffed (you may verify this by asking on the radio) for requests to be accepted and responded to.

Section IV > The Testing Process

Any test, interview, etc etc will follow very similar procedures for each type. Follow the steps below to learn more!

Develop a Test Question 

All tests you perform will require a test question, a statement that provides a question for your test to answer and/or solve. Without a test question, there would be no reason to conduct a test, as how can you learn anything if you don’t know what you’re looking to learn? Test questions should be creative while still being reasonable and feasible. An example of a test question is as follows: “Does SCP-131 take a liking towards higher-ranked Personnel in comparison to lower-ranked Personnel?”. 

While you are thinking of a test question, you should make sure that the test question is ethical by checking the CoE. If you wish to conduct a mass, unethical, or termination attempt test you must make a request within #special-test-requests. Check the channel for more information on who to ping and how to make each type of request.

Sometimes, the anomalies may require approval, specialized procedures, strict handling, and etc. You may check the AIM in that case. The document also includes which combative group is the anomaly under, spectation regulations, testing regulation, etc. The AIM is only meant as an extension to the CoE and does not supersede it.


Develop a Hypothesis 

A hypothesis is a prediction as to what will happen during your test. Your hypothesis should answer your test question while also providing a reason as to why you believe your prediction to be what will happen. Put more simply, you shouldn’t just guess what will happen, you need to provide a reason for your prediction otherwise it’s just an uneducated guess.

Requesting Outside Personnel

If your event requires an Anomaly/Lore Actor, or a combative that is not currently in game (such as Eta-9), you must go to the Joint Departmental Communications server and fill the format out in #event-request or #event-scheduling to request the appropriate people. Make sure to include a timestamp of your test using Hammertime so that those you are requesting can know much easier! Ensure you request for all the appropriate personnel for your event in the same request, no need to make multiple.

Request times:


Personnel for each location:

If there is no response from the requested escort for briefing after 5+ minutes, you may ping the next group in line. This means, if you've been waiting at the top of the Pit for 5 minutes for Eta to escort you into MCZ, you may ping Delta-1 next. Remember, request for combative personnel in game before pinging them in the joint server!

Make sure to read the Containment Zone Operating Procedures page for information on each Containment Zone.


Requesting Class-Ds & Combatives 

Once you've made your #event-request (if you need to), open the "Requests" radio in game and request whatever number of Class-D and SD you require. Make sure to request as little Class-D as necessary, as we don't want to waste resources and personnel! Remember, the ratio is 3 CD : 1 SD.


Use the following format to request CDs and SD:


Requesting an Object SCP

If your test uses an Object SCP located within the Loading Bay, you must request for it in the same manner you would as for Class-D/combatives. Make sure to send this request before you send your Class-D and combative request.


Use the following format to request LB SCPs:


Containment Checkpoint 

Once you arrive at any containment checkpoint, get into a single file line in the order of Host > Co-Hosts (if any) > Class-D > Spectators (if any). You will be briefed by SD, MP, or MTF depending on which containment zone you are in and whether a response was given or not. Ensure you listen to all orders given by combatives.


If your test is in the Pit (LCZ, MCZ, or HCZ) you will need to exit your vehicle and enter the small building seen below. If your test is in the Clean Rooms, you will line up in front of the scanner in front of the air lock.

During and After Test 

During your test, make sure to document what is happening. Take pictures, notes, and more! The higher tier your test report, the more detail you're going to need, and thus the more notes from your test. If your Class-D(s) seem to forget what you told them, don't be discouraged! Make sure to remind them of their task(s) and issues strikes to non-compliant Class-D. 


For information on each Containment Zone, read the Containment Zone Operating Procedures page.

Once you finish your test, you will need to submit a test report. There are three tiers (one to three) based on complexity. All three tiers are submitted in the #test-submissions channel, each with their own format. Refer to the pinned message in the channel and the Grading Rubric for more information!


Discovery Submissions

The discovery program aims to incentivize more creative and interesting tests, researchers can earn extra points from making discoveries during their tests. The amount of points can vary per the importance of the discovery, for example finding the origin of a SCP would be deemed more important than finding how fast 173 can move.


More information on #discovery-submission can be found on the Discord server.

Section V > Rewarding Class-Ds

After the test is completed it is required to reward the participating Class-Ds through the Terminal on-site.

At the terminal run the following command:


reward <Class-D> "Test Participation" <Rating from 1 to 10>

 

If you are rewarding multiple Class Ds remember to put a comma between the names of the Class Ds.

The rating will give 100 credits at 1 and 1300 at 10. 


You are required to reward Class-Ds for participating in your test, and proof of the terminal input must be provided in your test log.

This documentation was created and approved by Central Command.