Subscribe to rss feed

Enginering Process planning | General | Forum

 
You must be logged in to post user permissions login Login register Register


Register? | Lost Your Password?

Search Forums:


searchicon 






Minimum search word length is 3 characters – Maximum search word length is 84 characters
Wildcard Usage:
*  matches any number of characters    %  matches exactly one character

topic

Enginering Process planning

print
small tagNo Tags
UserPost

3:07 am
March 12, 2010


Luke Maurits

Adelaide, Australia

Admin

posts 1483

offline
link
print
41
0
ratedowngrey
rateupgrey

brmj said:I like this aproach as well. I don't think cash prizes are an option at this point, though, and I am not sure what it would do to the culture of open collaboration we are trying to cultivate to offer cash prizes internally.


Having thought about it more, I think a cash prize for this is probably a bad idea.  The overall competig proposal idea, though, I think is a good once and I think our next big IRC meeting should focus on the details of this as one of its higher priorities (although the agenda for the meeting is quite large so we shouldn't neglect too much else for the sake of this).

Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.

9:08 am
March 14, 2010


rpulkrabek

Member

posts 348

offline
link
print
42
0
ratedowngrey
rateupgrey

First of all, I should apologize for my absence. I have been quite busy with work and will continue to be quite busy. With in the next few months I may be doing quite a bit of traveling, but I will be sure to always follow along with the progress.

I wanted to make a few proposals for the engineering process. I had completed a project about a year ago that involved these methods I will explain. Unfortunately, I don't think I am allowed to share the actual data with everyone, but I am capable of explaining what was done.

With any new project, It is mandatory to list the objectives and constraints. With these, we can then weigh these appropriately, provide an evaluation criteria and the target and acceptable limits. These would look something like this, although much more complete (this is a very quick attempt on my part and in no way realistic):

mouse

From these, we can then decide a few initial concepts. For example, we could say we wanted to use either liquid fuel rocket, solid fuel or hybrid fuel. We can then create what is called a Pugh Matrix. We choose one method as our datum, and then then go down the list of our objectives and constraints and decide if the other methods are better, the same or worse than the datum. If in the end, one system is better, that then becomes our new datum and we repeat the process until we are satisfied. This would look something like this:

mouse

This matrix would of course be more complete and thought out to deal with our choices more precisely. I hope you understand the point. This method then provides us a way to document our decisions and why we chose them.

5:53 am
March 16, 2010


Luke Maurits

Adelaide, Australia

Admin

posts 1483

offline
link
print
43
+1
ratedowngrey
rateupgrey

Sorry I've not been as active lately as I usually am.  This might continue for a while.  Anyway, some more thoughts on the CLLARE proposal process:

First of all, with regards to what proposals must include, some basic ideas:

  • A proposal name
  • Brief overview of entire proposal (one or two paragraphs at most)
  • A list of core hardware items involved (e.g. CM, OSM, PM, LL for "Old Cllare")
  • Basic flight plan: is the proposal direct ascent, Earth orbit rendezvous, Lunar orbit rendezvous, or a mixture of these?  What does lunar landing look like?
  • Explanation of candidate reentry mechanisms: Ballistic?  Parachute?  Paraglider?  Ballute?  MOOSE?)
  • Proposed launch vehicle (must be an existing vehicle available for commerical launch – the Falcon 9 should count as existing)
  • Calculations (using the rocket equation) showing the proposal can reasonably fit on its proposed launch vehicle.  These don't need to be super precise, but they should be fairly realistic and not rely upon extremely optimistic estimates of hardware masses.  Maximum Isp which may be assumed is 450 s.

A proposal may include anything else that the people working on it think will improve the chances of it being selected, but the above is the mandatory bare minimum.  Any proposal which doesn't get the above sorted out by the day that voting opens will not be in the running.  It should also be noted that very fine details, like navigation hardware, etc., are not, I think, really appropriate for locking down at the proposal stage.  That stuff will be figured out using the Design Task Tree voting system.  The function of the proposal system is to lock down the high-level details of the project so that the Design Task Tree system can be set up.  For this reason, at the proposal stage, the "new" CLLARE plan should not speak of the spherical nature of its CM.  Instead it should merely emphasise that the CM doubles as a lander (which is the core of the plan).  CM shape can be decided using the tree system later.

Second of all, a more general thoughts: I am slightly concerned that we might not get a lot of new proposals coming in from our community (who are fairly quiet, at least for now).  It would make the proposal system somewhat silly and a waste of time if there ended up being precisely two proposals, the "old" one and the "new" one that has motivated the proposal system, and all we worked on from here on in was the "new" proposal.  To help counter this, perhaps we should "seed" the system with some very preliminary ideas and let the community expand on ones it finds interesting.  Some ideas:

  • The "ultra lightweight" approach that is advocated by Open Luna and by MicroSpace (a GLXP contender) – no spacecraft per se, the astronaut spends the whole trip in a pressure suit, seated/strapped in a minimalist, open-cab frame that provides propulsion and communications (example image).  I am not a huge fan of this approach, personally, but it does represent the ultimate embodiment of our Design Philosophy, so we should, I suppose, not exclude it without doing the research to confirm that it is not appropriate.  One nice thing about it is that the "spacecraft" would have such little mass we could probably replace LOX/LH2 liquid engines with hybrid rockets.
  • Something based around the concept of inflatable habitats, like the very successful Genesis modules of Bigelow Aerospace.  A CLLARE proposal with an inflatable (or partially inflatable) CM and/or LL would be very interesting, possibly helping significantly to keep vehicle mass down.
  • Something based on the idea of high horizontal velocity landing.  This would involve landing on the moon with significant horizontal velocity (but minimal vertical) and using skids, an air cushion, the lander structure or some combination thereof to "skid" to a halt.  This certainly makes safety/reliability more difficult, but it could potentially save us a lot of mass in the form of lander propellant.  This plan would require a landing site with a long stretch of clear ground to land on – maybe we can find something like this using Google Moon or the like?

A final consideration: How long do we want to give the community time to develop proposals before we call a vote?  We need to allow enough time for all the proposals to receive a fair amount of consideration, but if we leave it too long, interest in the project might wane.  We don't want a situation where the basic feasibility analyses have been done for all the proposals and there's not much else to do until the vote is called, but there's still a month to go.  Do people think that two months would be about right?  More?  Less?

(rpulkrabek: I don't mean to completely ignore your post about Pugh matrices etc. by just posting this – I wrote this up offline and have just pasted it now.  I will reply to your post separately soon).

Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.

6:26 pm
March 16, 2010


brmj

Rochester, New York, United States

Member

posts 402

offline
link
print
44
0
ratedowngrey
rateupgrey

I don't really have time at the moment for a reply as lengthy as I would like. I'll try to do that tonight or, worst case scenerio, tommorow. Sorry.

I see nothing in your proposal that I particularly object to.

I am currently in the process of designing another CLLARE proposal based on a high horizontal velocity landing. Let me say now that there were studies of this by Krafft Ehricke in the late 70s and early to mid 80s that looked rather promising, and at least one suitible landing site was identified, so this may not be as crazy as it first sounds.

My first thought on the two month time frame is that it looks reasonable, but I haven't given it all that much concideration. I'll get back to you on that when I do the expanded post.

Main work groups: Propulsion (booster), Spacecraft Engineering, Computer Systems, Navigation and Guidance (software)

8:29 pm
March 16, 2010


Luke Maurits

Adelaide, Australia

Admin

posts 1483

offline
link
print
45
0
ratedowngrey
rateupgrey

brmj said:

Let me say now that there were studies of this by Krafft Ehricke in the late 70s and early to mid 80s that looked rather promising, and at least one suitible landing site was identified, so this may not be as crazy as it first sounds.


Hey, that's great!  I had assumed this would turn out to be quite infeasible, at least without seriously violating simplicity, but if there's actually something to it then this could turn out to be an interesting proposal.

Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.

2:51 am
March 17, 2010


Luke Maurits

Adelaide, Australia

Admin

posts 1483

offline
link
print
46
0
ratedowngrey
rateupgrey

Rpulkrabek, I've read your post now, it looks quite sensible and looks like it will integrate fairly well with what we have so far.  The set of initial requirements and constraints is basically what we would use to constrain proposals, which would be high level overviews.  Once a proposal is chosen, we use something like a Pugh matrix to make decisions.  This gels well with the Design Task Tree approach.  Each node on the tree is a slice of the Pugh matrix.

One important thing this brings up with regards to the CLLARE proposal process is that we need to set requirements and constraints.  The only real requirement is the ability to land one (1) human on the surface of the moon and return them to a hospitable part of the Earth in good health.  I suppose a "bonus requirement" might be the ability to do sample return.  As for constraints, I think the only constraint we have so far (aside from the constraints on all CSTART projects imposed by the Social Contract and Design Philosophy) is that the system be compatible with an existing launch vehicle (e.g. Falcon 9).

Unrelated to Rpulkarbek's post, I thought of something else that every proposal should be required to have.  A list of major challenges/obstacles that need to be overcome, which are unique to that proposal, not to CLLARE as a whole.  For instance, the "new" CLLARE plan involving a CM that is also used as a lander raises the unique problem of needing a system to deal with lunar dust entering the CM.  This isn't a problem in the "old" CLLARE plan since then the astronaut could dust-off while on the lander in lunar orbit before transferring to the CM (although they'd still have to de-suit in the CM, so it is something of a problem).  Or, the ultra lightweight approach of OpenLuna / Microspace in which the astronaut spends the whole time in a suit with no enclosing spacecraft at all raises the unique problem of needing a fantastically good suit.  Neither the helmet nor the suit can be removed at any stage in this proposal, so things like food and drink supply and waste disposal all need to be completely buit in and need to work flawlessly for at least one week.  This is well beyond any previously constructed EVA suit, so it definitely counts as a major challenge.

I suppose in order to be fair we should also allow a list of selling points, to counter balance the major challenges and make sure we are rejecting proposals not just because they are challening (challenges lead to innovation!), but because their challenges are disproportionate to their big bonuses.

Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.

6:11 am
March 20, 2010


Luke Maurits

Adelaide, Australia

Admin

posts 1483

offline
link
print
47
0
ratedowngrey
rateupgrey

Possible basis for another CLLARE proposal: the LEAP "lunar ambulance".  Something like this perhaps pull off a balloon-cushioned skid landing?  The biggest challenge would be keeping an ascent engine intact during that landing.  Alternately, perhaps it could land softly, vertically upright?  Such a design would not be entirely unlike the Tycho Brahe.

Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.

6:54 am
March 20, 2010


Rocket-To-The-Moon

Altus, Oklahoma, USA

Member

posts 685

offline
link
print
48
0
ratedowngrey
rateupgrey

What advantage does a skid landing have? There is still going to be a considerable vertical velocity component that must be absorbed and then you have to deal with avoiding terrain features along the path of the skid. To me it sounds like an overly dangerous method with no apparent benefit.

Main Workgroups: Propulsion & Spacecraft Engineering

6:56 am
March 20, 2010


Luke Maurits

Adelaide, Australia

Admin

posts 1483

offline
link
print
49
0
ratedowngrey
rateupgrey

The benefit of a skid landing would be significant savings in the delta-v required for landing, and hence in propellant mass.

It's admittedly quite unorthodox and may not be worth pursuing, but I'd at least like to see it considered.  Finding suitably obstacle-free landing sites should be quite easy with the sheer volume of high resolution photos of the surface one can access on the web these days.

Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.

8:04 am
March 20, 2010


Rocket-To-The-Moon

Altus, Oklahoma, USA

Member

posts 685

offline
link
print
50
0
ratedowngrey
rateupgrey

The upper bounds of what I would consider reasonable would be maybe 30m/s horizontal velocity. That is probably only a couple of seconds of engine firing and a few kg of propellant. We would also need skis and the center of gravity would need to be low enough that it can't upset. The added mass of the skids over a traditional legged configuration would probably offset any savings. This is just a intuitive guess, but I agree that it is worth considering in more detail to see if it could work.

Main Workgroups: Propulsion & Spacecraft Engineering

12:06 pm
March 29, 2010


Clicker

US-Arizona

Member

posts 11

offline
link
print
51
0
ratedowngrey
rateupgrey

Post edited 1:41 pm – March 29, 2010 by Clicker


Hey all,

I'm here to help!  I haven't read through the whole thread yet to see where you're at just wanted to throw something up to let you all know that I would like to get started on this.  I'm going to read through everything now to see where we're at and whenever you get a chance let me know where you'd like me to start.

For those that haven't already seen it short bio is below, I'm a pretty good PHP dev with plenty of SQL experience.

http://cstart.org/forum/welcom…..-member-2/

EDIT: Ok I think I have a decent idea of what you want as far as the web app is concerned.  I have a work related project that I need to finish today-tomorrow but then I'm pretty much done for the week so I should have some time this week to work on something.  I'll check back later in the week to get started on the web app.

Computer Systems Design (IT) & Web Developer

5:49 pm
March 29, 2010


Luke Maurits

Adelaide, Australia

Admin

posts 1483

offline
link
print
52
0
ratedowngrey
rateupgrey

It's fantastic to see someone keen to have a start at this!

Do you have any idea what you will need in developing this?  Obviously our server has PHP available, and I am fairly sure the database is MySQL.  If you want/need any frameworks or libraries or anything, Rizwan should be able to tell you what is available/compatible.

Oh, and it goes without saying that we'd really like this web app to be open source.  We have a Mercurial repository associated with our Google Code project, if you want to use that for development of the web app we can absolutely set you up with an account.

Thanks very much for your interest in helping us out, this will be a huge help!

Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.

12:02 am
March 30, 2010


brmj

Rochester, New York, United States

Member

posts 402

offline
link
print
53
0
ratedowngrey
rateupgrey

Thanks! It will be great to see this getting started.

I can confirm that MySQL is in use on our site.

If you have any questions, comments, suggestions or concerns relating to this or need any help, don't hesitate to post something.

Main work groups: Propulsion (booster), Spacecraft Engineering, Computer Systems, Navigation and Guidance (software)

12:41 am
March 31, 2010


Luke Maurits

Adelaide, Australia

Admin

posts 1483

offline
link
print
54
0
ratedowngrey
rateupgrey

Post edited 2:32 am – March 31, 2010 by Luke Maurits


I have made some quite significant changes to the Engineering Process wiki page.  There's nothing on there which has not previously been mentioned either in this thread or on IRC and either received support or not provoked disagreement, so I hope nobody objects, but if people could have a look over it and make sure they are comfortable with these changes it would be appreciated.

There is still work to be done, but I think most of the details for the beginning of the process are in place, and we are probably read to officially start the proposal process for CLLARE (if we could do this on April 01 it would be kind of nice).  Obviously OHKLA and CLLARE have not been run to this process and we will have to "go back" and do a few things to make it look as if we did, but it would be great if the RedditCubeSat project could follow the proper process from scratch.

Particular shortcomings:

  • We need to make a decision on how voting will work.  From the Wiki: "Two proposals for the voting process are as follows: in the simplest option, members simply vote directly on solutions (IMPORTANT POINT: One vote for the "best" or preferential voting from 1-5, say?). In the more complicated option, members vote on how well each solution satisfies various criteria (simplicity, reliability, performance, etc.) and also vote on the relative importance of those criteria. The "winning" solution is that with the highest "score": a weighted sum of scores for each criteria. This second solution raises the problem of where the criteria come from. Do we have one fixed list of criteria for all decisions, or does the community need control over the criteria? If so, how do we give them that control?"  Let's discuss this!
  • There is nothing in there about physically building and testing stuff and feeding the results of testing back into the engineering process.
  • The Software Engineering Process is complete vapourware.

Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.

11:57 am
April 1, 2010


Clicker

US-Arizona

Member

posts 11

offline
link
print
55
0
ratedowngrey
rateupgrey

Post edited 12:02 pm – April 1, 2010 by Clicker


Hey all, I'm back on this now just starting to think about how to tackle a couple of the issues you're currently having.  Now for starters I'm not that familiar with this particular forum that you're using (shouldn't be hard to figure out once I get a copy of it), but I'm currently focused around 1 issue:

If we use the forum as a sole login for everything, we will also need to implement some kind of permissions system.  Though it seems you haven't been through this before, allowing everybody to edit everything (I'm thinking of the wiki specifically, and later the voting/issues system) is going to end up with some issues down the road.  There are lots of people out there that would figure out they could make an account and go on there and just destroy all of the documentation, or just generally screw things up.

I've started a new thread here: http://cstart.org/forum/miscel…..tes/#p2811

This is for a focus around just the web development stuff.

Do you have any idea what you will need in developing this?  Obviously our server has PHP available, and I am fairly sure the database is MySQL.  If you want/need any frameworks or libraries or anything, Rizwan should be able to tell you what is available/compatible.

Oh, and it goes without saying that we'd really like this web app to be open source.  We have a Mercurial repository associated with our Google Code project, if you want to use that for development of the web app we can absolutely set you up with an account.

PHP/MySQL is what I expected you'd have, and that's perfect, this is what I'm most familiar with.  As for what I need to get started, I don't think there would really be any special extensions needed for anything proposed (so far) just PHP with the usual default extensions should be fine.  The only thing I would need is some method to upload changes to the site.

I've never used Mercurial before but it looks pretty nice, it'd be great if I could get an account.  I'd like to start of course by setting up the single sign on system, as that would make it easier to build the issues/voting system later (building up on the single sign on — instead of coming back to that later).  For now I'll just get started familiarizing myself with Simple:Press forum so I can see what's needed to get the single sign on working.

EDIT: Sorry it kind of seems like I'm hijacking this thread now, I'm going to post more thoughts in the new thread.

Computer Systems Design (IT) & Web Developer

small tagNo Tags

About the CSTART – Collaborative Space Travel and Research Team Forum

Forum Timezone: UTC -6

Most Users Ever Online: 59

Currently Online:
13 Guests

Currently Browsing this Topic:
2 Guests

Forum Stats:

Groups: 4
Forums: 36
Topics: 512
Posts: 3809

Membership:

There are 1133 Members

There are 2 Admins

Top Posters:

Rocket-To-The-Moon – 685
brmj – 402
rpulkrabek – 348
DenisG – 69
antinode – 64
J. Simmons – 46

Recent New Members: jmwright, uhwuggawuh, seikialice88, bishvabis, alijayadv, harris

Administrators: Luke Maurits (1483 Posts), Rizwan (170 Posts)



 
share save 120 16