Talk:SEDSAT-2 IAC 2007 Paper

From SEDSWiki

Jump to: navigation, search

Contents

Michael's Comments

(coment -what are we trying to say by saying technical assets? do we mean that this paper will explain in complete detail how the satellite is constructed, where we got all the components, etc?--Michael 17:30, 18 February 2007 (EST)).

(general coment: We need to decide if possible what the mission objective of this project is. Is it to observe the earth, or 'celestial objects', or to test advanced technology, or test many advanced technologies, or both, or what? One of the main comments from the mission concept review board was that we would have our hands full just getting the thing up there in the first place, much less doing anything really fancy. We also have budget constraints to wory about. If our mission objective is to test out new technology, we probably won't be able to pay for it, we would have to have it donated. also, I recall that wireless communications had been droped from the list of probable missions, along (I believe) with interferometry -sterio imaging ;)

I would be further tempted to change the mission objectives paragraph to something like this:

The objective of this mission is primarilly the experience to be gained by the students throughout the project. Secondary more specific objectives include successfully carying out pre-launch testing, followed by establishing communication with the satellite once in orbit, establishing control over it's attitude, taking pictures with it (probably of the earth), and finally, successfully recovering those images, perhaps toward the goal of creating a spaceflight video.

--Michael 17:30, 18 February 2007 (EST)).

Editions:

Paragraph 1: (changed from " with international participation. It's the second satellite " --Michael 17:30, 18 February 2007 (EST)).

Paragraph 2:

(changed from "The mission objetives are taking pictures of celestial bodies or earth and acting as a test bed for advanced technologies into attitude control system, interferometry and wireless communications between onboard equipments. " --Michael 17:30, 18 February 2007 (EST)).

Paragraph 3:

(changed from "One of the main challenges of this project is the way of coordinating every people involved and who live in different sides of the world. Some tools have been developed for this task: blog, wiki and Protoforge (changed from "other own software" to Protoforge --Pradeep 16:35, 8 February 2007 (IST)). At the same time, other widespread communications software is used to facilitate this. " --Michael 17:30, 18 February 2007 (EST)).


Lavina's Comments

  • added a new paragraph on a short introduction of the CubeSat (Paragraph '0')
  • I think that since we don't have the payload yet, we should concentrate on the mission being the international collaboration part: to provide experience for students in satellite building where the components are built separately all over the world and integrated later on.
  • I'm not very aware, but exactly which software will we be using to design (and coordinate) the different subsystems? I'm talking about AutoCAD, etc.

Title:

  • [Original Version]

SEDSAT-2. A TECHNOLOGY DEMOSTRATION CUBESAT WITH INTERNATIONAL COLABORATION. (changed from "A TECHNOLOGY DEMOSTRATOR WITH INTERNATIONAL PARTICIPATION CUBESAT --Michael 17:30, 18 February 2007 (EST)).


Paragraph 1:

  • [Original version] by members of the organization, Students for the Exploration and Development of Space (SEDS) using international collaboration.
  • [Original Version] The first mission, SEDSAT-1, was designed by members of SEDS-USA and launched as a secondary payload aboard the Deep Space 1 mission in 1998.

Paragraph 2:

  • The mission objectives are taking pictures of either celestial bodies or earth and acting as a test bed for experimental technologies to provide attitude control, and to perform interferometry, and perhaps wireless communications between onboard components.

Paragraph 3:

  • Among the main challenges of this project is coordinating all the people involved who live throughout the world
  • Some tools have been developed for this task: a blog, a wiki and Protoforge (changed from "other own software" to Protoforge --Pradeep 16:35, 8 February 2007 (IST))An e-mail list is also used for communication, as well as either msn or skype for online meetings. As the project devellops, google calenday may be used for scheduling.

Lavina's Comments

If the corrections simply involve word changes, then you can post the original version here in the discussion sections and refer to them by numbering the paragraphs

Michael's Comments

I added a part to paragraph 2 specifying what the technical mission might actually be. I think this is important, because without it, there is really no information about what we are planing on doing, and for all anybody else knows, we may or may not know what we are doing, we might be putting a bomb up there, or we might believe we can do some incredibly intricate experiment, or who knows what. Something like this send the message that we are aware of what these satellites can do (generally speaking), and that our goal is deliberatly simple, allowing us to focus on making sure the thing works.

Paragraph 4:

  • [Original version]In this paper will be shown all aspects of this project, especially those with regard to management, teams coordination and technical assets. [This is too vague. Abstracts still need to be specific. This means naming the "technical assets", and the various ways the team is managed and coordinate. When I say name, I mean just that: name. No detailed explanations :) ]

Pradeep's Comments

  • Changed from: "SEDSat-2's technical mission objective will likely involve remote sensing, possibly as simply as taking one or more pictutes of the earth during the life time of the mission." to a new paragraph 3 and corresponding changes in paragraph numbers.
  • Do we need so many details for authors/co-authors?

Reply to Pradeep

  • *Do we need so many details for authors/co-authors? --> Yes, according to the guidelines for IAC abstract submission. Check the links in the notes section. However, we can email that info to the "Contact Author," presumably the person submitting the abstract, and he'll add it. Adding such detail to the wiki is not a good idea; which is why I didn't do it. The addition of the fields themselves I found necessary so that it would not be forgotten in the rush to meet the deadline that seems inevitable.--Lavina

Further reply to Pradeep

  • In that case, we aught to all send out information to the contact author now, so we don't forget! So who is the contact author? --Mike.

Reply to Mike

If you want, you can send it to me and I'll post it up on Google Docs so that anyone on the team can access it, but no one outside the team. How does that sound?

Reply to Pradeep?

That is pradeep speaking I presume?

Reply to Question

Lavina, actually. Sorry, I was in a hurry so forgot to sign my name

Aaron's comments

  • I am wondering if section (0) should be the first section in your abstract?

Probably want to start with section (2). Let the reader know what the paper is really about up front. Then Section (1), then (3)

  • Wording related:
    • "wherein separate components are designed and developed separately"...

No need to say separately twice, I suggest: "wherein subsystems are designed and developed by geographically separated teams"

    • "Tools that have been developed for this task"...

implies that the blog/wiki/protoforge software was developed just for the sedsat-2 project I suggest "New technology and tools will be used to maximize the coordination between our globally distributed team. These tools include a blog, a wiki"...

  • section (5) might be refined a little too.

Reply to Aaron

  • Incorporated your suggestions --Lavina
  • (4) [Original Version] "As the project develops, Google Calendars may be used for scheduling." --Lavina

Lavina's Comments

  • Integrated paragraphs 2 and 3 and numbered it as 2

[Original Version](2) SEDSat-2's primary mission objective is to provide students from around the world with experience in satellite development wherein subsystems are designed and developed by geographically separated teams and later integrated into a functioning system

(3) SEDSAT-2's primary payload will be a digital imager to do visible spectrum remote sensing. The secondary payload will be decided on the basis of applications received from student-members.

Mike's Comments

I have made aditional changes to the first three sections. Here are the originals in case the changes are not satisfactory.

With these changes, section (0) now only contains historical information of no direct importance to what our satellite will do, or how it will be constructed, etc. These changes provide the option, if such a possibility ever became desirable, to leave out section (0) completelly without compromizing on transmiting important information. Espetially if the target audience already knows about the cubesat program and it's history. With that said, it does not mean that I am in favour of such an option.

What I have now done is to move this section to the end, and referenced it in the first so that readers who are not familiar with the cubesat program can bring themselves up to date, while the continuity of the description of the actual project is not broken for those readers already familiar with the program.

[Original Version](0,1,2)

(1) SEDSAT-2 is a CubeSat project that will be designed and built by members of the organization, Students for the Exploration and Development of Space (SEDS) through international collaboration. It is the second satellite mission designed by SEDS. The first mission, SEDSAT-1, was designed by members of SEDS-USA, developed at the University of Alabama in Huntsville, and launched as a secondary payload aboard the Deep Space 1 mission in 1998.

(0) The California Polytechnic Institute's CubeSat program aims to facilitate small satellite development in universities and private firms, by obtaining export licenses and approvals as well as providing a "standard, reliable, and flight proven deployment system called the Poly Picosatellite Orbital Deployer, or P-POD." [1]

(2) SEDSAT-2's primary payload will be a digital imager to do visible spectrum remote sensing. The secondary payload will be decided on the basis of applications received from student-members. The satellite's primary mission objective, however, goes beyond the payload; it is to provide students from around the world with experience in satellite development wherein subsystems are designed and developed by geographically separated teams and later integrated into a functioning system.


Reply to Mike

These are good revisions :) -- Lavina

Nirupam's Comments

  • I have few comments on the current version of the abstract (in case this is not THE final version, we can modify these subject to other member's opinion). (i) This abstract seems marginally lengthier than that of a standard technical paper. (ii) Though some of the international journals (e.g. Astronomy & Astrophysics) have abstract format broken into few parts (with headings like context, aims, methods, results and conclusion for A&A), it is a standard practise to have a single paragraph for abstract (Is there anything specified by IAC?). (iii) Item zero (after item 1) seems to be a break in the continuation and came suddenly without adequate contex. Nirupam 17:20 UTC, 27 February, 2007


Reply to Nirupam

With reference to the paragraph breaks, I completely agree with you. That was one of my first thoughts as I started editing the abstract, but I left it as it is for only one reason: editing convenience. The way it is now, there is relative ease in reformatting, rephrasing or reorganizing the abstract, with convenient reference points.

In the final editing, however, you are right: the abstract should flow as one paragraph. :) I'm sure the person who does the editing will take this into account, and if he/she doesn't, then we can all ask him/her to.

Also, on a completely unrelated note, my parents are from Pune. We go there every couple of years. I was just there in 2005 looking into studying at IIT :)---Lavina


Lavina's Comments

  • [Original Version] (1) SEDSAT-2 is a CubeSat project -see section (0)- that will be designed and built by members of the organization, Students for the Exploration and Development of Space (SEDS) through international collaboration.
  • (2) digital imager to do visible spectrum remote sensing
  • Paragraph 4: We need to finalize the software we're going to use to develop and integrate the systems. I suggest Celestia and SolidWorks along with Google SketchUp or Blender for rough ideas.
  • [original version] (0) The California Polytechnic Institute's CubeSat program aims to facilitate small satellite development in universities and private firms, by obtaining export licenses and approvals as well as providing a "standard, reliable, and flight proven deployment system called the Poly Picosatellite Orbital Deployer, or P-POD." [2] SEDSAT-2 is the second satellite mission designed by SEDS. The first mission, SEDSAT-1, was designed by members of SEDS-USA, developed at the University of Alabama in Huntsville, and launched as a secondary payload aboard the Deep Space 1 mission in 1998.
    • I deleted the entire (merged) paragraph 0 because it was looking more and more out of place. Really, it now looks like the beginnings of an introduction to the paper (which we really should start working on). But if you guys want it in there or think that it looks better in there, go ahead and include it again :)

Reply to lavina

I deleted the entire (merged) paragraph 0 because it was looking more and more out of place. Really, it now looks like the beginnings of an introduction to the paper (which we really should start working on). But if you guys want it in there or think that it looks better in there, go ahead and include it again :)

I agree :) So let's do that! If my memory serves me right (it might not) you were the one who originally proposed putting something like this at the begining of the abstract? -mike

Further reply to lavina

I have made a stab at the above, and found it necessary to modify the first paragraph of the abstract. here is the original version:

(1) SEDSAT-2 is a picosatellite, under the CubeSat program, that will be designed and built by members of the organization Students for the Exploration and Development of Space (SEDS) through international collaboration.

Reply to Mike

That's good. I just expanded SEDS so it flows better.

(1) [Original version] SEDSAT-2 is a picosatellite, under the CubeSat program, that will be designed and built by the Students for the Exploration and Development of Space (SEDS)--Lavina

Reply to Lavina

I'm not sure I completely understand what you did... your original version (1) is the same as is now in the abstract... As I understand it, the original version is shorter than this one.

Also, the introduction is now at the end, where a conclusion should be. Is it ment to act as a history or background? If so, should we call it that: Background (as opposed to introduction).


Reply to Mike

  • I simply expanded SEDS, as abbreviations are seldom used in formal documents without a prior introduction.
  • The reason the Introduction is now at the end was because I figured you'd started an Introduction to the paper as opposed to that of an abstract. I really don't think our abstract needs separate components like an Introduction. What do you guys think?

Reply to lavina

I have changed the introduction to background. However, I am not convinced that the material contained therein is appropriate. I believe it needs to be re-worded, or removed entirelly. Does our target audience know about seds? sedsat1? the cubesat program? will they be expecting us to explain all these things? If they know about them, we should leave this part out. How knowledgeable are they? It seems to me likely that they will be aware of this history.

actually, re-reading lavina's comment, I think I now understand. The introduction that i wrote should be more of an introduction to the paper itself, destinct to the abstract. If this is to make up part of the paper, then unless we really need to define these things for the abstract, I would not include them.

Further Reply to lavina

Following kirk's e-mail, I have taken the liberty of removing the introduction/background section from the abstract. The section is copy-pasted below for reference. -mike

==Background==

The California Polytechnic Institute's CubeSat program aims to facilitate small satellite development in universities and private firms, by obtaining export licenses and approvals as well as providing a "standard, reliable, and flight proven deployment system called the Poly Picosatellite Orbital Deployer, or P-POD." [3]

Students for the Exploration and Development of Space (SEDS) is an organization of students interested in space that originated in the US, and now has chapters in many countries throughout the world.

SEDSAT-1 was a satellite mission that was designed by members of SEDS-USA, developed at the University of Alabama in Huntsville, and launched as a secondary payload aboard the Deep Space 1 mission in 1998.


Lavina's Editions

This version was proposed by Kirk, and I modified it a bit to make it flow better. Here's Kirk's original version:

SEDSAT-2 is a picosatellite, under the CubeSat program, that will be designed and built by Students for the Exploration and Development of Space (SEDS) through international collaboration. The design team includes students in Austria, Canada, Germany, India, Italy, Nigeria, Norway, Philippines, Russia, Spain, United Kingdom, and United States. The proposed launch of SEDSAT-2 is in 2009. The primary payload of SEDSAT-2 will be a digital imaging device for remote sensing in the visible spectrum. The secondary payload will be decided on the basis of applications received from student-members. The primary mission objective, however, goes beyond the payload; it is to provide students from around the world with experience in satellite development wherein subsystems are designed and developed by geographically separated teams and later integrated into a functioning system. Among the main challenges of this project is coordinating globally distributed participants. New as well as existing technologies and tools will be used to maximize the coordination between our globally distributed team. These tools include a blog, a Wiki and a decision-making and planning site called ProtoForge.org. In this paper will be laid out all the rules and procedures that will have been developed and adopted throughout the project with regards to project management and coordination, and technical communication between teams. It will also include detailed technical descriptions and diagrams of the satellite and each of its subsystems and components, along with discussions of alternative technologies and systems, trade studies for choosing specific designs. The SEDSAT-2 Preliminary Design Review will be held at the Vellore Institute of Technology in Vellore, India, on 22 September 2007, in conjunction with the SEDS International Conference.

Retrieved from "http://wiki.seds.org/index.php/Talk:SEDSAT-2_IAC_2007_Paper"
Personal tools