|
This False Data Stripping module is not really a beginner's module. There are three things the user needs to be familiar with in order to get good results from this module:
The first two are fairly obvious, but the third one isn't. It could be that the only way to get familiar with it is to do the procedure a bit and find out that way by trial and error. The usual error is that one continues on past the point where one should have ended off, and one is trying to work with something that isn't there any more. Nothing drastic is likely to happen if one does this, other than feeling that there is something wrong with the procedure as it isn't working out properly. So just be aware that this is a possibility if things start going wrong in session. The theory of FDSing is here. It is assumed that you are already familiar with Rub & Yawn and have had successful sessions using it. And that before starting a session you will have taken the necessary steps to be fully sessionable. Before assuming that you need FDSing, check out this page first. The end point for a False Data Stripping session is covered in FDS: End Points. You should have a WRITTEN C/S (Case Supervisor instruction) for the session before you start. You can write this yourself if you don't have someone else acting as C/S (Case Supervisor). The reason for writing it is so that you know what you will be doing in the session, and don't go off on some wild tangent. It is usually a bad idea to do a session without a written C/S which you keep to in session. If the C/S (instruction) turns out to not be working in session, then end off the session and write a different C/S outside of session. Great! Let's do the full pre-session check to make sure I'm ready for the session. I'm familiar with what is needed. Let's go with the final check! |
|