[roc-chat] Re: Separate LPR area at ROCtober
- From: Richard Dierking <richard.dierking@xxxxxxxxx>
- To: "roc-chat@xxxxxxxxxxxxx" <roc-chat@xxxxxxxxxxxxx>
- Date: Tue, 26 Jun 2012 17:27:46 -0700
How did the RSO become the rocket inspector and most of the time they have
their back to the range?
Richard
Sent from my iPhone
On Jun 26, 2012, at 3:56 PM, "Ken Curran" <rocket1dog@xxxxxxx> wrote:
> Not much said about the RSO duties...
>
>
>
>
> -------Original Message-------
>
> From: Michael Klett
> Date: 6/26/2012 3:14:37 PM
> To: roc-chat@xxxxxxxxxxxxx
> Subject: [roc-chat] Re: Separate LPR area at ROCtober
>
> Mike,
>
> I always try to take at least one shift during the big launch weekends
> and I'm willing to take more if I'm going to be there long enough.
> I'm willing to cover a shift on a regular launch weekend as well but
> often my son takes that for the family - he really likes doing it.
>
> You had said, "For instance, if someone feels that lack of
> information/training is an issue, why not approach the board, request
> the info, and produce materials to rectify the situation? Or, if the
> info doesn't exist, offer to develop it? Would it really take that
> much more time and effort to do that than was spent commenting on the
> lack of it?" Umm, actually, I had never thought of it until Rick
> mentioned it and my first thought was, "Hey, that's really cool! I
> wish I would've known that before." I did what I thought was my best
> impersonation of what I had seen other people do before me, basically
> OJT. I had taken the slow times so it wasn't too bad. So basically,
> I would've happily help develop it if I had realized that I had needed
> it. I do need to spend more time on the lake bed learning. And I
> discuss it here because it is one thing that I can do now between
> launches. I'm happy for all of this discussion as I am learning so
> much.
>
> And since e-mail can be such a terrible way of communicating I do want
> to assure you that this post isn't intended to be a flame, purely
> informational. If it came across as a flame I apologize. My feathers
> are NOT ruffled, my spirits are bright, I'm having a really good day
> today, and I'm looking forward to flying in just two and a half weeks.
> I wish the same for you.
>
> Thanks,
> Mike
>
> On Tue, Jun 26, 2012 at 2:58 PM, Mike Riss <rockt_dude@xxxxxxxxxxxxx> wrote:
> > I'm not sure that waiting for 30 minutes is necessarily bad. It's surely
> > not optimum, but if
> > there are 45+ pads, and if almost every pad is occupied, that's something
> > less than 1 minute
> > processing time per pad.
> >
> > And, is it really an issue, or just unrealistic expectations? Given that
> > we have difficulty
> > filling range duty slots, is it realistic to expect volunteers to meet the
> > *ideal* performance level?
> >
> > And, do these discussions create a self-fulfilling prophecy by discouraging
> > people from not
> > volunteering because they don't want to be lambasted for less than ideal
> > performance either on
> > the 'Chat, or as sometimes happens in person?
> >
> > Not looking to discourage discussion, but I wonder: if the same (as in "in
> > addition to", not
> > "instead of") amount of time and effort was spent *doing* something as is
> > spent discussing it,
> > would there still be an issue?
> >
> > For instance, if someone feels that lack of information/training is an
> > issue, why not approach
> > the board, request the info, and produce materials to rectify the
> > situation? Or, if the info doesn't exist, offer to develop it? Would it
> > really
> > take that much more time and effort to do that than was spent commenting on
> > the lack of it?
> >
> > Looks like some info previously existed, but didn't get ported to the
> > current website:
> >
> > http://web.archive.bibalex.org/web/20060222064909/www.rocstock.org/rules.lcos.html
> >
> > Looks like there was also info for RSO and PM. Between this and Rick D's
> > post, shouldn't take
> > much time or effort to resolve this particular issue.
> >
> > But I guess, just like filling range duty slots, people will wait until
> > someone -- as in,
> > someone *else* -- does something about it :-(
> >
> > Mike
> >
> > --
> > ROC-Chat mailing list
> > roc-chat@xxxxxxxxxxxxx
> > //www.freelists.org/list/roc-chat
> >
>
> --
> ROC-Chat mailing list
> roc-chat@xxxxxxxxxxxxx
> //www.freelists.org/list/roc-chat
>
Other related posts:
