rocketworkbench-devel

[Rocketworkbench] Debian Rocketworkbench package

[Geoff O'C. <ge...@st...>]

Greetings,

Just a FYI.

I've packaged 'rocketworkbench' as a Debian GNU/Linux package.  Those of you 
using Debian can get the package from 'unstable' via apt-get.

The package currently only has 'cpropep' in it.  But i'll incorporate other 
utilities in new versions of the package.

Enjoy.

Cheers
Geoff

RV: [Rocketworkbench] Cpropep frozen perfomance calculations.]

[<ghe...@ci...>]

Dear Antoine and rocketworkbench colleagues,

I think the frozen perfomance calculations are now o.k. Most important,
entropy values are now constant at the three sections during expansion. The
subsisting differences in the output results with the example given in NASA
RP-1311, Mc Bride and Gordon, Part II, Users Manual and Program
Description,1996, could well be explained by differences in the heat of
formation of the ingredients and mainly by the fact that composition is
frozen in the  NASA example, not at chamber conditions, but from the throat
section (point 2)downwards, as can be appreciated comparing gas composition
with the corresponding equilibrium perfomance calculations.
For your information, please find attached a file with the relevant pages
(160-164) with the results from the example of the NASA report. I will try
to scan results of an example of  true frozen perfomance calculation fom
chamber downwards, from  the now classical  NASA SP-273, Gordon and Mc
Bride, 1973, and send it to you, so you can check your results more
properly. The NASA reports can be downloaded from
http://techreports.larc.nasa.gov
Antoine, thank you very much for your work and efforts. Cpropep is really a
fine contribution to rocket perfomance calculations and I'm using it already
for my lectures on Propulsion at the Army's Technical High School.
With best regards and wishes for futher success,

Gunterio Heineken

 

[Rocketworkbench] RV: Cpropepshell interfase 1.01

[<ghe...@ci...>]

-----Mensaje original-----
De: Hans Olaf Toft [mailto:ho...@vi...]
Enviado el: Mi=E9rcoles, 12 de Septiembre de 2001 06:56 p.m.
Para: ghe...@ci...
Asunto: Re: Cpropepshell interfase 1.01


Hi Gunterio
Glad to hear that everything is working. The text error on the =
userinterface
is
caused by tha fact that I actually write the text during program =
execution,
and
has made a cut and paste error - but while composing the layout I also =
have
defined the texts and they are correct, so I have simply overlooked =
this
matter.
I will correct it in the comming days.

I have also observed the "freezing of the previous result" You describe =
but
I
have really no idea what causes it - until further I will blame =
windows...

Regards
Hans

"Heineken, Gunterio Germ=E1n" wrote:

> Dear Hans Olaf,
>
> Finally we got the complete result in the output text window. We
reinstalled
> the files and solved the problem we had with maximizing.
> With reference to the second area ratio input option this was also
> clarified: the obtained results, in spite of the reading, correspond =
in
fact
> to  subsonic exit to throat area, so that we have really both =
distinct
input
> area options, which is a very good thing. I assume the corresponding =
input
> reading can easyly be corrected in future versions.
> Sometimes, when we return from the text to the input window and =
simply
> change perfomance conditions with the same ingredients and run, we =
get, we
> don't know really why, immediately after "please wait",  the text =
window
> with the results of the previous calculations, and this may be, has  =
added
> some confusion regarding the  results with area ratio inputs.
> Since the interface does not allow the input of only one component, =
in the
> case of monopropellants, like hydracine, we succeeded in splitting =
the
same
> component in two parts and amounts. Again thank you for your prompt =
reply
> and your help.
> Regards,
>
> Gunterio.
>
> Gunterio,
>
> I will need more information before I can solve any problems:
>
> The Cpropepshell works in the following way:
> 1) Pressing the "run" button creates a file "temporary.pro" as =
cpropep
> input.
> 2) Cpropepshell asks Windows to run the cpropep with the command line
> parameters
> required for specifying temporary.pro as input and standard out =
redirected
> to a
> file named "temporary.out".
> 3) Cpropepshell waits until Windows signals that the cpropep process =
has
> terminated.
> 4) The temporary.out is displayed in a text window.
>
> This means that the complete result *should* show up in the text =
window.
If
> this
> does not happend, then, please check that the temporary.out holds the
> complete
> information. If windows signals that the cpropep process has =
terminated
> before
> flushing the temporary.out strange things could happend.
>
> OTOH, You mention that it "helps" (?) to print or save - does this =
make
the
> missing texts show up?
>
> Hans
>
> "Heineken, Gunterio Germ=E1n" wrote:
>
> > Dear Olaf,
> >
> > In the meantime I checked the cpropepshell 1.01 interfase and it =
works
> > pretty well for the selected exit conditions. I had only a small =
trouble
> > with the  output data, which did not appear  fully displayed, but =
this
can
> > be solved by  saving the results on the Note Block or by printing. =
By
the
> > way, would it not be more meaningful to have as additional input =
option,
> for
> > exit conditions, the subsonic area ratio, as cpropep-web allows, =
instead
> of
> > two supersonic area ratios giving both the same results?
> > Again thank you for your contribution which I appreciate very much =
and
> which
> > will be, no doubt, very useful for practical use and educational
training.
> > Best regards and hoping to hear from you and our colleagues from =
the
> > Rocketworkbench,
> >
> > Gunterio Heineken
> > Buenos Aires, Argentina.

[Rocketworkbench] RE: Cpropepshell interfase 1.01

[<ghe...@ci...>]

Dear Hans Olaf,

Finally we got the complete result in the output text window. We =
reinstalled
the files and solved the problem we had with maximizing.
With reference to the second area ratio input option this was also
clarified: the obtained results, in spite of the reading, correspond in =
fact
to  subsonic exit to throat area, so that we have really both distinct =
input
area options, which is a very good thing. I assume the corresponding =
input
reading can easyly be corrected in future versions.
Sometimes, when we return from the text to the input window and simply
change perfomance conditions with the same ingredients and run, we get, =
we
don't know really why, immediately after "please wait",  the text =
window
with the results of the previous calculations, and this may be, has  =
added
some confusion regarding the  results with area ratio inputs.
Since the interface does not allow the input of only one component, in =
the
case of monopropellants, like hydracine, we succeeded in splitting the =
same
component in two parts and amounts. Again thank you for your prompt =
reply
and your help.
Regards,

Gunterio.=20


Gunterio,

I will need more information before I can solve any problems:

The Cpropepshell works in the following way:
1) Pressing the "run" button creates a file "temporary.pro" as cpropep
input.
2) Cpropepshell asks Windows to run the cpropep with the command line
parameters
required for specifying temporary.pro as input and standard out =
redirected
to a
file named "temporary.out".
3) Cpropepshell waits until Windows signals that the cpropep process =
has
terminated.
4) The temporary.out is displayed in a text window.

This means that the complete result *should* show up in the text =
window. If
this
does not happend, then, please check that the temporary.out holds the
complete
information. If windows signals that the cpropep process has terminated
before
flushing the temporary.out strange things could happend.

OTOH, You mention that it "helps" (?) to print or save - does this make =
the
missing texts show up?

Hans


"Heineken, Gunterio Germ=E1n" wrote:

> Dear Olaf,
>
> In the meantime I checked the cpropepshell 1.01 interfase and it =
works
> pretty well for the selected exit conditions. I had only a small =
trouble
> with the  output data, which did not appear  fully displayed, but =
this can
> be solved by  saving the results on the Note Block or by printing. By =
the
> way, would it not be more meaningful to have as additional input =
option,
for
> exit conditions, the subsonic area ratio, as cpropep-web allows, =
instead
of
> two supersonic area ratios giving both the same results?
> Again thank you for your contribution which I appreciate very much =
and
which
> will be, no doubt, very useful for practical use and educational =
training.
> Best regards and hoping to hear from you and our colleagues from the
> Rocketworkbench,
>
> Gunterio Heineken
> Buenos Aires, Argentina.

[Rocketworkbench] Cpropepshell interfase 1.01

[<ghe...@ci...>]

Dear Olaf,

In the meantime I checked the cpropepshell 1.01 interfase and it works
pretty well for the selected exit conditions. I had only a small =
trouble
with the  output data, which did not appear  fully displayed, but this =
can
be solved by  saving the results on the Note Block or by printing. By =
the
way, would it not be more meaningful to have as additional input =
option, for
exit conditions, the subsonic area ratio, as cpropep-web allows, =
instead of
two supersonic area ratios giving both the same results?
Again thank you for your contribution which I appreciate very much and =
which
will be, no doubt, very useful for practical use and educational =
training.
Best regards and hoping to hear from you and our colleagues from the
Rocketworkbench,

Gunterio Heineken
Buenos Aires, Argentina.
 =20

Send Rocketworkbench-devel mailing list submissions to
	roc...@li...

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.sourceforge.net/lists/listinfo/rocketworkbench-devel
or, via email, send a message with subject or body 'help' to
	roc...@li...

You can reach the person managing the list at
	roc...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Rocketworkbench-devel digest..."


Today's Topics:

   1. Re: GUI for cpropep (Hans Olaf Toft)
   2. RV: Rocketworkbench-devel digest, Vol 1 #46 - 2 msgs, Rocketworkb
       ench-devel digest, Vol 1 #47 - 1 msg
(=3D?iso-8859-1?Q?=3D22Heineken=3D2C_Gunterio_Germ=3DE1n=3D22?=3D)

--__--__--

Message: 1
Date: Sat, 25 Aug 2001 12:01:33 +0200
From: Hans Olaf Toft <ho...@vi...>
To: Rocket Workbench <roc...@li...>
Subject: [Rocketworkbench] Re: GUI for cpropep


--------------C80044D8C2DF7A24889046D6
Content-Type: text/plain; charset=3Diso-8859-1
Content-Transfer-Encoding: 8bit


"Heineken, Gunterio Germ=E1n" wrote:

> I found that cpropepShell interface works well for adiabatic flame
> temperature and fixed pressure and temperature calculations , but I =
had
> trouble with exit pressure and area ratio imput data for frozen and
shifting
> equilibrium conditions.

The validity check error on the exit conditions is now fixed. An =
additional
error of loosing the fixed pressure and temperature problem has also =
been
removed.

The updated cpropepshell 1.01 is awailable from
http://users.cybercity.dk/~dko7904/cpropepshell/cpropepshell.htm

Also the full (Delphi 4) source is now awailable from the same =
location. The
original download has been removed.

Hans Olaf Toft


--------------C80044D8C2DF7A24889046D6
Content-Type: text/html; charset=3Dus-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>"Heineken, Gunterio Germ&aacute;n" wrote:
<blockquote TYPE=3DCITE>I found that cpropepShell interface works well =
for
adiabatic flame
<br>temperature and fixed pressure and temperature calculations , but I
had
<br>trouble with exit pressure and area ratio imput data for frozen and
shifting
<br>equilibrium conditions.</blockquote>
The validity check error on the exit conditions is now fixed. An =
additional
error of loosing the fixed pressure and temperature problem has also =
been
removed.
<p>The updated cpropepshell 1.01 is awailable from
<br><a
href=3D"http://users.cybercity.dk/~dko7904/cpropepshell/cpropepshell.htm=
">http
://users.cybercity.dk/~dko7904/cpropepshell/cpropepshell.htm</a><a
href=3D"http://users.cybercity.dk/~dko7904/cpropepshell/cpropepshell.htm=
"></a>
<p>Also the full (Delphi 4) source is now awailable from the same =
location.
The original download has been removed.
<p>Hans Olaf Toft
<br><a
href=3D"http://users.cybercity.dk/~dko7904/cpropepshell/cpropepshell.htm=
"></a>
&nbsp;</html>

--------------C80044D8C2DF7A24889046D6--



--__--__--

Message: 2
From: =3D?iso-8859-1?Q?=3D22Heineken=3D2C_Gunterio_Germ=3DE1n=3D22?=3D
	 <ghe...@ci...>
To: 'ho...@vi...'
Cc: ant...@so...,, ant...@po...,,=20
	roc...@li...
Date: Fri, 24 Aug 2001 17:21:54 -0300
Subject: [Rocketworkbench] RV: Rocketworkbench-devel digest, Vol 1 #46 =
- 2
msgs, Rocketworkb
 ench-devel digest, Vol 1 #47 - 1 msg





Dear Olaf,

I was using your most welcomed cpropepShell interface. I found that it =
has
more calculation options than Gpep, which allows only for shifting
equilibrium performance evaluation. Your interface  has similar options =
 as
Cpropep-web http://rocketworkbench.sourceforge.net/equil.phtml=20
but allows calculations for systems with more than three components, =
which
is a limitation of cpropep-web.
I found that cpropepShell interface works well for adiabatic flame
temperature and fixed pressure and temperature calculations , but I had
trouble with exit pressure and area ratio imput data for frozen and =
shifting
equilibrium conditions. In general for this calcultions, as Gpep and
cpropep-web  require, for a given chamber pressure, either exit =
pressure or
supersonic area ratio are selected, but not both at the same time, =
since
they are functionally related. CpropepShell interface requires input of =
both
exit pressure and two? supersonic area ratios. The result is that we =
obtain
incorrect exit parameters for the selected input data, which do not
correspond either to the selected exit pressure nor to the area ratio, =
and
the outprint never gives the input exit pressure back. Output values =
for
chamber and throat sections  are o.k. and identical to those obtained =
with
Gpropep and cpropep-web interfaces. May be you can help to overcome =
this
trouble.
Thank you very much for your effort.
Best regards and wishes.

Gunterio Heineken

CITEFA
Buenos Aires, Argentina


 -----Mensaje original-----
De: roc...@li...
[mailto:roc...@li...]
Enviado el: Martes, 21 de Agosto de 2001 04:06 p.m.
Para: roc...@li...
Asunto: Rocketworkbench-devel digest, Vol 1 #46 - 2 msgs


Send Rocketworkbench-devel mailing list submissions to
	roc...@li...

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.sourceforge.net/lists/listinfo/rocketworkbench-devel
or, via email, send a message with subject or body 'help' to
	roc...@li...

You can reach the person managing the list at
	roc...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Rocketworkbench-devel digest..."


Today's Topics:

   1. GUI for Cpropep (Hans Olaf Toft)
   2. Re: GUI for Cpropep (Antoine Lefebvre)

-- __--__--=20

Message: 1
Date: Mon, 20 Aug 2001 23:18:04 +0200
From: Hans Olaf Toft <ho...@vi...>
To: roc...@li...
Subject: [Rocketworkbench] GUI for Cpropep

I have made a small application - nothing special really - that =
provides a
graphical userinterface for cpropep under
Windows.

For those interested, it may be found at
http://users.cybercity.dk/~dko7904/DARK/download/cpropepshell.zip

The application need to be located in the same directory as cpropep.exe =
and
cpropep.conf.

Hans Olaf Toft



-- __--__--=20

Message: 2
Date: Tue, 21 Aug 2001 00:21:21 -0400
From: Antoine Lefebvre <an...@sh...>
To: Rocket Workbench <roc...@li...>
Subject: Re: [Rocketworkbench] GUI for Cpropep
Reply-To: ant...@so...

Note that there is another GUI for windows at =
http://www.msu.edu/user/asman
called Gpep. I will put links for both application on the web page.

Is the source code for your application available ?

Thanks for your work.

On Mon, Aug 20, 2001 at 11:18:04PM +0200, Hans Olaf Toft wrote:
> I have made a small application - nothing special really - that =
provides a
graphical userinterface for cpropep under
> Windows.
>=20
> For those interested, it may be found at
> http://users.cybercity.dk/~dko7904/DARK/download/cpropepshell.zip
>=20
> The application need to be located in the same directory as =
cpropep.exe
and cpropep.conf.
>=20
> Hans Olaf Toft
>=20
>=20
> _______________________________________________
> http://rocketworkbench.sourceforge.net
> Rocketworkbench-devel mailing list
> Roc...@li...
> http://lists.sourceforge.net/lists/listinfo/rocketworkbench-devel

--=20
Antoine Lefebvre
ant...@po...



-- __--__--=20

_______________________________________________
Rocketworkbench-devel mailing list
Roc...@li...
http://lists.sourceforge.net/lists/listinfo/rocketworkbench-devel


End of Rocketworkbench-devel Digest


Send Rocketworkbench-devel mailing list submissions to
	roc...@li...

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.sourceforge.net/lists/listinfo/rocketworkbench-devel
or, via email, send a message with subject or body 'help' to
	roc...@li...

You can reach the person managing the list at
	roc...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Rocketworkbench-devel digest..."


Today's Topics:

   1. Re: GUI for Cpropep (Hans Olaf Toft)

-- __--__--=20

Message: 1
Date: Tue, 21 Aug 2001 23:52:45 +0200
From: Hans Olaf Toft <ho...@vi...>
To: roc...@li...
Subject: [Rocketworkbench] Re: GUI for Cpropep




> Note that there is another GUI for windows at
http://www.msu.edu/user/asman
> called Gpep. I will put links for both application on the web page.

I wasn't really aware of that, so maybe I could have spared the efford.
However it was quite fun to do and I learned a
couple of things during the process, so maybe the only drawback is that
there are now  two different interfaces for
Windows and none for other platforms.

> Is the source code for your application available ?

In principle yes, but it is very sparsely commented (uncommented
actually...) so I would like to add a few comments if
source code is to be made public. Source code is written in Delphi - it
could maybe be ported to Linux with some limited
efford.

> Thanks for your work.

- Cpropep itself is the real achivement, so thanks for Your work
Antoine!

Hans Olaf Toft



-- __--__--=20

_______________________________________________
Rocketworkbench-devel mailing list
Roc...@li...
http://lists.sourceforge.net/lists/listinfo/rocketworkbench-devel


End of Rocketworkbench-devel Digest



--__--__--

_______________________________________________
Rocketworkbench-devel mailing list
Roc...@li...
http://lists.sourceforge.net/lists/listinfo/rocketworkbench-devel


End of Rocketworkbench-devel Digest

Re: [Rocketworkbench] Cpropep frozen perfomance calculations.

[Antoine L. <an...@sh...>]

The problem you report is interesting. I will not be able to look at that before
the end of september but am very interested to solve it.

I will give feedback as soon as I find the problem.

Keep me inform if any of you have any clues.

Thanks

-- 
Antoine Lefebvre
ant...@po...

[Rocketworkbench] Cpropep frozen perfomance calculations.

[<ghe...@ci...>]

Dear rocketworkbench-devel colleagues,

During frozen perfomance calculations with Cpropep using either Cpropep-Web
on line  or the recent  CpropepShell interfases I noticed  rather important
discrepancies with the values presented for the example given in NASA RP
1311, pages 163 -4, specially lower  throat and exit temperatures and throat
entropy. Surprisingly for me using Cpropep for frozen perfomance calculation
the obtained  entropy value at throat is lower than the  values at  chamber
and exit sections and not equal as should be the case for an isoentropic
expansion, regardless of equilibrium or frozen conditons, as illustrated in
the mentioned example of the NASA report.. This is not the case for shifting
perfomance calculations where all the values match very well the example
values with constant entropy values for all three sections and equal to the
cooresponding  values at  chamber and exit conditions for frozen conditions.
The input heat of formation data for the components used in Cpropep are
slightly different from those of the example, but seem to affect very little
the output data, at least for shifting perfomance. Please find attached
files with the calculation results. I hope someone can help to explain and
resolve the differences.

Gunterio Heineken
Buenos Aires, Argentina

 <<frozen_perform.htm>>  <<shift_perform.htm>> 

[Rocketworkbench] Re: GUI for cpropep

[Hans O. T. <ho...@vi...>]

"Heineken, Gunterio Germán" wrote:

> I found that cpropepShell interface works well for adiabatic flame
> temperature and fixed pressure and temperature calculations , but I had
> trouble with exit pressure and area ratio imput data for frozen and shifting
> equilibrium conditions.

The validity check error on the exit conditions is now fixed. An additional
error of loosing the fixed pressure and temperature problem has also been
removed.

The updated cpropepshell 1.01 is awailable from
http://users.cybercity.dk/~dko7904/cpropepshell/cpropepshell.htm

Also the full (Delphi 4) source is now awailable from the same location. The
original download has been removed.

Hans Olaf Toft

[Rocketworkbench] RV: Rocketworkbench-devel digest, Vol 1 #46 - 2 msgs, Rocketworkb ench-devel digest, Vol 1 #47 - 1 msg

[<ghe...@ci...>]

Dear Olaf,

I was using your most welcomed cpropepShell interface. I found that it has
more calculation options than Gpep, which allows only for shifting
equilibrium performance evaluation. Your interface  has similar options  as
Cpropep-web http://rocketworkbench.sourceforge.net/equil.phtml 
but allows calculations for systems with more than three components, which
is a limitation of cpropep-web.
I found that cpropepShell interface works well for adiabatic flame
temperature and fixed pressure and temperature calculations , but I had
trouble with exit pressure and area ratio imput data for frozen and shifting
equilibrium conditions. In general for this calcultions, as Gpep and
cpropep-web  require, for a given chamber pressure, either exit pressure or
supersonic area ratio are selected, but not both at the same time, since
they are functionally related. CpropepShell interface requires input of both
exit pressure and two? supersonic area ratios. The result is that we obtain
incorrect exit parameters for the selected input data, which do not
correspond either to the selected exit pressure nor to the area ratio, and
the outprint never gives the input exit pressure back. Output values for
chamber and throat sections  are o.k. and identical to those obtained with
Gpropep and cpropep-web interfaces. May be you can help to overcome this
trouble.
Thank you very much for your effort.
Best regards and wishes.

Gunterio Heineken

CITEFA
Buenos Aires, Argentina


 -----Mensaje original-----
De: roc...@li...
[mailto:roc...@li...]
Enviado el: Martes, 21 de Agosto de 2001 04:06 p.m.
Para: roc...@li...
Asunto: Rocketworkbench-devel digest, Vol 1 #46 - 2 msgs


Send Rocketworkbench-devel mailing list submissions to
	roc...@li...

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.sourceforge.net/lists/listinfo/rocketworkbench-devel
or, via email, send a message with subject or body 'help' to
	roc...@li...

You can reach the person managing the list at
	roc...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Rocketworkbench-devel digest..."


Today's Topics:

   1. GUI for Cpropep (Hans Olaf Toft)
   2. Re: GUI for Cpropep (Antoine Lefebvre)

--__--__--

Message: 1
Date: Mon, 20 Aug 2001 23:18:04 +0200
From: Hans Olaf Toft <ho...@vi...>
To: roc...@li...
Subject: [Rocketworkbench] GUI for Cpropep

I have made a small application - nothing special really - that provides a
graphical userinterface for cpropep under
Windows.

For those interested, it may be found at
http://users.cybercity.dk/~dko7904/DARK/download/cpropepshell.zip

The application need to be located in the same directory as cpropep.exe and
cpropep.conf.

Hans Olaf Toft



--__--__--

Message: 2
Date: Tue, 21 Aug 2001 00:21:21 -0400
From: Antoine Lefebvre <an...@sh...>
To: Rocket Workbench <roc...@li...>
Subject: Re: [Rocketworkbench] GUI for Cpropep
Reply-To: ant...@so...

Note that there is another GUI for windows at http://www.msu.edu/user/asman
called Gpep. I will put links for both application on the web page.

Is the source code for your application available ?

Thanks for your work.

On Mon, Aug 20, 2001 at 11:18:04PM +0200, Hans Olaf Toft wrote:
> I have made a small application - nothing special really - that provides a
graphical userinterface for cpropep under
> Windows.
> 
> For those interested, it may be found at
> http://users.cybercity.dk/~dko7904/DARK/download/cpropepshell.zip
> 
> The application need to be located in the same directory as cpropep.exe
and cpropep.conf.
> 
> Hans Olaf Toft
> 
> 
> _______________________________________________
> http://rocketworkbench.sourceforge.net
> Rocketworkbench-devel mailing list
> Roc...@li...
> http://lists.sourceforge.net/lists/listinfo/rocketworkbench-devel

-- 
Antoine Lefebvre
ant...@po...



--__--__--

_______________________________________________
Rocketworkbench-devel mailing list
Roc...@li...
http://lists.sourceforge.net/lists/listinfo/rocketworkbench-devel


End of Rocketworkbench-devel Digest


Send Rocketworkbench-devel mailing list submissions to
	roc...@li...

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.sourceforge.net/lists/listinfo/rocketworkbench-devel
or, via email, send a message with subject or body 'help' to
	roc...@li...

You can reach the person managing the list at
	roc...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Rocketworkbench-devel digest..."


Today's Topics:

   1. Re: GUI for Cpropep (Hans Olaf Toft)

--__--__--

Message: 1
Date: Tue, 21 Aug 2001 23:52:45 +0200
From: Hans Olaf Toft <ho...@vi...>
To: roc...@li...
Subject: [Rocketworkbench] Re: GUI for Cpropep




> Note that there is another GUI for windows at
http://www.msu.edu/user/asman
> called Gpep. I will put links for both application on the web page.

I wasn't really aware of that, so maybe I could have spared the efford.
However it was quite fun to do and I learned a
couple of things during the process, so maybe the only drawback is that
there are now  two different interfaces for
Windows and none for other platforms.

> Is the source code for your application available ?

In principle yes, but it is very sparsely commented (uncommented
actually...) so I would like to add a few comments if
source code is to be made public. Source code is written in Delphi - it
could maybe be ported to Linux with some limited
efford.

> Thanks for your work.

- Cpropep itself is the real achivement, so thanks for Your work
Antoine!

Hans Olaf Toft



--__--__--

_______________________________________________
Rocketworkbench-devel mailing list
Roc...@li...
http://lists.sourceforge.net/lists/listinfo/rocketworkbench-devel


End of Rocketworkbench-devel Digest

[Rocketworkbench] Re: GUI for Cpropep

[Hans O. T. <ho...@vi...>]

> Note that there is another GUI for windows at http://www.msu.edu/user/asman
> called Gpep. I will put links for both application on the web page.

I wasn't really aware of that, so maybe I could have spared the efford.
However it was quite fun to do and I learned a
couple of things during the process, so maybe the only drawback is that
there are now  two different interfaces for
Windows and none for other platforms.

> Is the source code for your application available ?

In principle yes, but it is very sparsely commented (uncommented
actually...) so I would like to add a few comments if
source code is to be made public. Source code is written in Delphi - it
could maybe be ported to Linux with some limited
efford.

> Thanks for your work.

- Cpropep itself is the real achivement, so thanks for Your work
Antoine!

Hans Olaf Toft

Re: [Rocketworkbench] GUI for Cpropep

[Antoine L. <an...@sh...>]

Note that there is another GUI for windows at http://www.msu.edu/user/asman
called Gpep. I will put links for both application on the web page.

Is the source code for your application available ?

Thanks for your work.

On Mon, Aug 20, 2001 at 11:18:04PM +0200, Hans Olaf Toft wrote:
> I have made a small application - nothing special really - that provides a graphical userinterface for cpropep under
> Windows.
> 
> For those interested, it may be found at
> http://users.cybercity.dk/~dko7904/DARK/download/cpropepshell.zip
> 
> The application need to be located in the same directory as cpropep.exe and cpropep.conf.
> 
> Hans Olaf Toft
> 
> 
> _______________________________________________
> http://rocketworkbench.sourceforge.net
> Rocketworkbench-devel mailing list
> Roc...@li...
> http://lists.sourceforge.net/lists/listinfo/rocketworkbench-devel

-- 
Antoine Lefebvre
ant...@po...

[Rocketworkbench] GUI for Cpropep

[Hans O. T. <ho...@vi...>]

I have made a small application - nothing special really - that provides a graphical userinterface for cpropep under
Windows.

For those interested, it may be found at
http://users.cybercity.dk/~dko7904/DARK/download/cpropepshell.zip

The application need to be located in the same directory as cpropep.exe and cpropep.conf.

Hans Olaf Toft

[antoine: Re: [Rocketworkbench] Propellant.dat format]

[Antoine L. <an...@sh...>]

-- 
Antoine Lefebvre
ant...@po...

[Rocketworkbench] Propellant.dat format

[Hans O. T. <ho...@vi...>]

The "propellant.dat" file comments its own format as
(A1,I5,A30,6(I3,A2),F5.0,F6.0)  and states that "A4, are flags"... How are
theese flags to be interpreted? - I can't get the propellant codes to match.

Hans Olaf Toft

[Rocketworkbench] new directory tree

[Antoine L. <an...@sh...>]

Hi ,

the source code in the rocketworkbench project have been reorganized and
a new cvs directory contain this new structure. Everything is now
located in the directory 'rocketworkbench'. Source have been divised between
libraries and executables, a Documentation directory will contain examples,
man pages and any other useful documentation. The building process
have also been change. Everything work ok on a linux platform. 

The rockflight program will be in active developmnent during next month.
Any contribution should be appreciate. It is a rocket trajectory simulator
that will include earth rotation, thrust vectoring, multiple stage, and
much more.

You could see all this on
http://sourceforge.net/projects/rocketworkbench and
http://rocketworkbench.sourceforge.net

Happy rocketry!

-- 
Antoine Lefebvre
ant...@po...

Re: [Rocketworkbench] Debian Packaging

[Geoff O'C. <ge...@st...>]

On Monday 02 July 2001 07:25, Antoine Lefebvre wrote:
> Hi Geoff,
> It have not been done yet. I would be happy if you do it.
> Are you a Debian developper ?? You don't seem to be listed on
> debian.org . Once you did the package, I could ask my brother
> to put it on the official distribution (he is a developper).
>

No... I'm not an official Debian developer - yet.  I'm going through the new 
maintainer process at the moment.  I've had a quick go at creating the 
package and at this stage it seems relatively straightforward.  I've got a 
few packaging questions and bug reports etc - can we discuss the packaging 
via the -devel list?  Should s/w bugs be via the sourceforge bugs system 
and/or here? - nothing major really.


> Thank you Geoff.
>

No problem... Geoff

Re: [Rocketworkbench] Debian Packaging

[Antoine L. <an...@sh...>]

Hi Geoff,
It have not been done yet. I would be happy if you do it.
Are you a Debian developper ?? You don't seem to be listed on 
debian.org . Once you did the package, I could ask my brother
to put it on the official distribution (he is a developper).

Thank you Geoff.

Antoine


On Sat, Jun 30, 2001 at 03:21:49PM +1000, Geoff O'Callaghan wrote:
> G'day,
> 
> Has anyone packaged (or working on packaging) 'rocketworkbench' as a Debian 
> package?  I can't seem to find any references to it.  I'm happy to package 
> the application if there are no objections??
> 
> Cheers
> Geoff
> 
> _______________________________________________
> http://rocketworkbench.sourceforge.net
> Rocketworkbench-devel mailing list
> Roc...@li...
> http://lists.sourceforge.net/lists/listinfo/rocketworkbench-devel

-- 
Antoine Lefebvre
ant...@po...

[Rocketworkbench] Debian Packaging

[Geoff O'C. <ge...@st...>]

G'day,

Has anyone packaged (or working on packaging) 'rocketworkbench' as a Debian 
package?  I can't seem to find any references to it.  I'm happy to package 
the application if there are no objections??

Cheers
Geoff

Re: [Rocketworkbench] Compile problems

[Antoine L. <an...@sh...>]

Hi,

my version work fine. I also update some change in the cvs, try downloading
the new version to see if it works.

Normally, the 'test' program should be compile after the library. I'm not
sure why your compiler seem to compile the test program first.

If you want, I could give you a temporary account on my computer in order
to talk directly. So I will be able to assist you directly for the compilation.
After you suceed, I could be a good idea if you write a Readme file for
windows compilation.


On Thu, Feb 22, 2001 at 11:10:39AM -0700, David Lautenschlager wrote:
> When trying to compile libnum I got the following error, there is no source
> or rules for -lnum or -lm.  Should PROG=test be removed from this make file,
> or does source/rules for num and m need to be added?
> 
> Thanks,
> 	Dave
> 
> $ make
> make -C src all
> make[1]: Entering directory `/rwb/libnum/src'
> gcc -g -Wall -O3  test.o -L../lib/ -lnum -lm -o test
> /usr/lib/gcc-lib/i686-pc-cygwin/2.95.2-6/../../../../i686-pc-cygwin/bin/ld:
> cann
> ot find -lnum
> collect2: ld returned 1 exit status
> make[1]: *** [test] Error 1
> make[1]: Leaving directory `/rwb/libnum/src'
> make: *** [all] Error 2
> 
> _______________________________________________
> http://rocketworkbench.sourceforge.net
> Rocketworkbench-devel mailing list
> Roc...@li...
> http://lists.sourceforge.net/lists/listinfo/rocketworkbench-devel

-- 
Antoine Lefebvre
ant...@po...

[Rocketworkbench] Compile problems

[David L. <dav...@mc...>]

When trying to compile libnum I got the following error, there is no source
or rules for -lnum or -lm.  Should PROG=test be removed from this make file,
or does source/rules for num and m need to be added?

Thanks,
	Dave

$ make
make -C src all
make[1]: Entering directory `/rwb/libnum/src'
gcc -g -Wall -O3  test.o -L../lib/ -lnum -lm -o test
/usr/lib/gcc-lib/i686-pc-cygwin/2.95.2-6/../../../../i686-pc-cygwin/bin/ld:
cann
ot find -lnum
collect2: ld returned 1 exit status
make[1]: *** [test] Error 1
make[1]: Leaving directory `/rwb/libnum/src'
make: *** [all] Error 2

Re: [Rocketworkbench] compilation

[Antoine L. <an...@sh...>]

Hi,
in order to compile the cpropep executable you must previously compile
three library: libcproprep, libthermo, libnum

These library are also in the cvs and you should also install them.
In reality, cpropep is only a program that read a description file
and use libcpropep functions to compute equilibrium and performance.

The philosophy behind that is to let us easily reuse the functionality
of cpropep to include in other program. By example, if you want a GUI
front end to cpropep, you could directly link with the library and use
the function. I also work on a program to simulate complete thrust curve
of a motor based on combustion equation that link with cpropep.


On Wed, Feb 21, 2001 at 11:43:10AM -0700, David Lautenschlager wrote:
> The Make file for the CVS version does not work in my GNU environment, the
> error follows. I was able to compile the CVS version using MS VC++ by moving
> all the files to a single directory.
> 
> $ make
> make -C src all
> make[1]: Entering directory `/rwb/cpropep/src'
> gcc -g -Wall -O3  cpropep.o -L../../libnum/lib -L../../libthermo/lib
> -L../../lib
> cpropep/lib -lcpropep -lthermo -lnum -lm   -o cpropep
> /usr/lib/gcc-lib/i686-pc-cygwin/2.95.2-6/../../../../i686-pc-cygwin/bin/ld:
> cann
> ot find -lcpropep
> collect2: ld returned 1 exit status
> make[1]: *** [cpropep] Error 1
> make[1]: Leaving directory `/rwb/cpropep/src'
> make: *** [all] Error 2
> 
> In the make file in the cpropep directory is the following rule:
> 
> $(PROG): $(OBJS) $(LIBNAME)
> 	$(CC) $(COPT) $(OBJS) $(LIBDIR) $(LIB) -o $@
> 
> But LIBNAME is not defined anywhere.  Do you have any environment variables
> set, or a special directory structure different from the CVS version?
I just forgot to remove this old rule, sorry.
> 
> Also, it would be convienient if there was a single CVS module to check out
> that included all the files needed to compile cpropep, instead of having to
> check out each directory individually.
Based on the previous explanation, I think it is better for the project
to be split in different library that could be reuse in diferent programs.

> 
> 
> $ make
> make -C src all
> make[1]: Entering directory `/rwb/cpropep/src'
> gcc -g -Wall -O3  cpropep.o -L../../libnum/lib -L../../libthermo/lib
> -L../../lib
> cpropep/lib -lcpropep -lthermo -lnum -lm   -o cpropep
> /usr/lib/gcc-lib/i686-pc-cygwin/2.95.2-6/../../../../i686-pc-cygwin/bin/ld:
> cann
> ot find -lcpropep
> collect2: ld returned 1 exit status
> make[1]: *** [cpropep] Error 1
> make[1]: Leaving directory `/rwb/cpropep/src'
> make: *** [all] Error 2

After you install and compile the three library, everything should work 
normally. Give me news about that. I'm happy to see that you are really 
interested in the project.


-- 
Antoine Lefebvre
ant...@po...

[Rocketworkbench] Make file

[David L. <dav...@mc...>]

According to the GNU make manual,  the .c suffix is part of the default
suffix list, so the line:

.SUFFIXES: .c

in the cpropep/src/makefile had no effect.

[Rocketworkbench] (no subject)

[David L. <dav...@mc...>]

The Make file for the CVS version does not work in my GNU environment, the
error follows. I was able to compile the CVS version using MS VC++ by moving
all the files to a single directory.

$ make
make -C src all
make[1]: Entering directory `/rwb/cpropep/src'
gcc -g -Wall -O3  cpropep.o -L../../libnum/lib -L../../libthermo/lib
-L../../lib
cpropep/lib -lcpropep -lthermo -lnum -lm   -o cpropep
/usr/lib/gcc-lib/i686-pc-cygwin/2.95.2-6/../../../../i686-pc-cygwin/bin/ld:
cann
ot find -lcpropep
collect2: ld returned 1 exit status
make[1]: *** [cpropep] Error 1
make[1]: Leaving directory `/rwb/cpropep/src'
make: *** [all] Error 2

In the make file in the cpropep directory is the following rule:

$(PROG): $(OBJS) $(LIBNAME)
	$(CC) $(COPT) $(OBJS) $(LIBDIR) $(LIB) -o $@

But LIBNAME is not defined anywhere.  Do you have any environment variables
set, or a special directory structure different from the CVS version?

Also, it would be convienient if there was a single CVS module to check out
that included all the files needed to compile cpropep, instead of having to
check out each directory individually.


$ make
make -C src all
make[1]: Entering directory `/rwb/cpropep/src'
gcc -g -Wall -O3  cpropep.o -L../../libnum/lib -L../../libthermo/lib
-L../../lib
cpropep/lib -lcpropep -lthermo -lnum -lm   -o cpropep
/usr/lib/gcc-lib/i686-pc-cygwin/2.95.2-6/../../../../i686-pc-cygwin/bin/ld:
cann
ot find -lcpropep
collect2: ld returned 1 exit status
make[1]: *** [cpropep] Error 1
make[1]: Leaving directory `/rwb/cpropep/src'
make: *** [all] Error 2

Re: [Rocketworkbench] CVS

[Antoine L. <an...@sh...>]

The command line options are

cvs -d:pserver:ano...@cv...:/cvsroot/rocketworkbench login

Also note that the zip file is an older version than the cvs one.


On Mon, Feb 19, 2001 at 09:52:11AM -0700, David Lautenschlager wrote:
> What should I enter as my CVSROOT to use CVS to checkout Cpropep?
> (should be easier than downloading the whole .zip each time).
> 
> Thanks,
> 
> Dave
> 
-- 
Antoine Lefebvre
ant...@po...

[Rocketworkbench] CVS

[David L. <dav...@mc...>]

What should I enter as my CVSROOT to use CVS to checkout Cpropep?
(should be easier than downloading the whole .zip each time).

Thanks,

Dave