<table border=0 cellpadding=2 cellspacing=“0”><tr><td><!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.0 Transitional//EN”>
<DIV><FONT face=“Arial” size=“2”>
<DIV><FONT face=“Arial” size=“2”>
<P class=“MsoNormal”><FONT face=“Arial” color=“navy” size=“2”><SPAN style=“FONT-SIZE: 10pt;COLOR: navy;FONT-FAMILY: Arial;”>Dear AnyBody Users,</SPAN></FONT></P>
<P class=“MsoNormal”><FONT face=“Arial” color=“navy” size=“2”><SPAN style=“FONT-SIZE: 10pt;COLOR: navy;FONT-FAMILY: Arial;”>My name is Nirjhar Dhang, and I am currently working in the AnyBody Research Group on development of an interface between the C3D file format and the AnyBody Modeling System. As you probably know, C3D is a standard file format for recording of movement data in gait analysis systems.</SPAN></FONT></P>
<P class=“MsoNormal”><FONT face=“Arial” color=“navy” size=“2”><SPAN style=“FONT-SIZE: 10pt;COLOR: navy;FONT-FAMILY: Arial;”>The 3D marker points along with the EMG and force plate data are stored in a binary formatted C3D file. Any Motion Capturing system, like VICON or QualiSYS has its own processing software, particularly for converting camera data for markers to 3D marker point data in the laboratory co-ordinate system. In the C3D file, each 3D marker point has a residual value which indicates the reliability of the data. The negative residual value indicates that the data is not acceptable, the positive value indicates the relative error and the zero value indicates that the data is computed rather than measured. Four popularly used marker sets are available for gait measurement. They are : a) Helen Hayes, b) Kit Vaughan, c) Cleveland Clinic and d) Mayo Clinic. In all these sets, fifteen markers are used. One more marker set is found in HIP98 CD distributed by the Free University of Berlin where 24 markers are used for measurement. However, only 15 land marks including joint centers are reported.</SPAN></FONT></P>
<P class=“MsoNormal”><FONT face=“Arial” color=“navy” size=“2”><SPAN style=“FONT-SIZE: 10pt;COLOR: navy;FONT-FAMILY: Arial;”>It is for processing this type of data that we are developing the C3D interface. The ultimate goal of this work is to be able to read movement data from a C3D file and seamlessly create an AnyBody model that will model the gait movement and simulate the forces in the musculoskeletal system.</SPAN></FONT></P>
<P class=“MsoNormal”><FONT face=“Arial” color=“navy” size=“2”><SPAN style=“FONT-SIZE: 10pt;COLOR: navy;FONT-FAMILY: Arial;”>Before we proceed we would like to hear the opinions you may have on the matter. The current status of the work is as follows:</SPAN></FONT></P>
<DIV>
<P class=“MsoNormal”><FONT face=“Times New Roman” color=“navy” size=“3”><SPAN style=“FONT-SIZE: 12pt;COLOR: navy;”> 1.</SPAN></FONT><FONT face=“Arial” color=“navy” size=“2”><SPAN style=“FONT-SIZE: 10pt;COLOR: navy;FONT-FAMILY: Arial;”>A program called C3D2Any has been developed. It is invoked by the following command line
C3D2Any <C3D file> <ANY | DAT file> [ANY | DAT ]
The last argument in the above command line is optional. If the last argument is not given, the output file will be written in AnyScript. </SPAN></FONT></P>
<P class=“MsoNormal”><FONT face=“Times New Roman” color=“navy” size=“3”><SPAN style=“FONT-SIZE: 12pt;COLOR: navy;”>2.</SPAN></FONT><FONT face=“Arial” color=“navy” size=“2”><SPAN style=“FONT-SIZE: 10pt;COLOR: navy;FONT-FAMILY: Arial;”>The program is prepared to have more features included for different output facilities, such as output of marker data only, or combination of marker data, EMG and force plate etc. This can be implemented by different command line arguments. </SPAN></FONT></P>
<P class=“MsoNormal”><FONT face=“Times New Roman” color=“navy” size=“3”><SPAN style=“FONT-SIZE: 12pt;COLOR: navy;”>3.</SPAN></FONT><FONT face=“Arial” color=“navy” size=“2”><SPAN style=“FONT-SIZE: 10pt;COLOR: navy;FONT-FAMILY: Arial;”>There is also a version available which builds upon the library supplied by the C3D organization (www.c3d.org). </SPAN></FONT></P>
<P class=“MsoNormal”><FONT face=“Arial” color=“navy” size=“2”><SPAN style=“FONT-SIZE: 10pt;COLOR: navy;FONT-FAMILY: Arial;”> </SPAN></FONT></P>
<P class=“MsoNormal”><FONT face=“Arial” color=“navy” size=“2”><SPAN style=“FONT-SIZE: 10pt;COLOR: navy;FONT-FAMILY: Arial;”></SPAN></FONT><FONT face=“Arial” color=“navy” size=“2”><SPAN style=“FONT-SIZE: 10pt;COLOR: navy;FONT-FAMILY: Arial;”>Where are we going from here? Well, we need to solve a number of problems before the C3D file can directly produce a workable AnyScript model.</SPAN></FONT></P>
<P class=“MsoNormal”><FONT face=“Times New Roman” size=“3”><SPAN style=“FONT-SIZE: 12pt;”></SPAN></FONT></P>
<P class=“MsoNormal”><FONT face=“Times New Roman” color=“navy” size=“3”><SPAN style=“FONT-SIZE: 12pt;COLOR: navy;”>a.<FONT face=“Times New Roman” size=“1”><SPAN style=“FONT: 7pt ‘Times New Roman’;”> </SPAN></FONT></SPAN></FONT><FONT face=“Arial” color=“navy” size=“2”><SPAN style=“FONT-SIZE: 10pt;COLOR: navy;FONT-FAMILY: Arial;”>The markers are attached on the surface of the body and errors are induced due to skin movement or by some other means. This introduces noise in the data. On the other hand, the data are redundant in the sense that we have more data than strictly necessary to identify the movement of each model segment in space. The problem is now how to process the noisy, redundant data to obtain joint centers. We have few ideas, but we would really appreciate your comments.</SPAN></FONT><FONT color=“navy”><SPAN style=“COLOR: navy;”> </SPAN></FONT></P>
<P class=“MsoNormal”><FONT face=“Times New Roman” color=“navy” size=“3”><SPAN style=“FONT-SIZE: 12pt;COLOR: navy;”>b.</SPAN></FONT><FONT face=“Arial” color=“navy” size=“2”><SPAN style=“FONT-SIZE: 10pt;COLOR: navy;FONT-FAMILY: Arial;”>Should we go for a solution that seamlessly converts the data to an AnyScript model in one step, or should we rather split the process into a few intermediate stages, for instance (1) filtering, (2) identification of the rigid body movement of each segment, (3) processing of the data to honor joint constraints. The advantage of having distinct steps is that it might enhance the user’s control of the process. What would you as users prefer?</SPAN></FONT><FONT color=“navy”><SPAN style=“COLOR: navy;”> </SPAN></FONT></P>
<P class=“MsoNormal”><FONT face=“Times New Roman” size=“3”><SPAN style=“FONT-SIZE: 12pt;”></SPAN></FONT></P>
<P class=“MsoNormal”><FONT face=“Arial” color=“navy” size=“2”><SPAN style=“FONT-SIZE: 10pt;COLOR: navy;FONT-FAMILY: Arial;”>Please post your comments in the group. We really appreciate your help.</SPAN></FONT></P>
<P class=“MsoNormal”><FONT face=“Times New Roman” size=“3”><SPAN style=“FONT-SIZE: 12pt;”></SPAN></FONT></P>
<P class=“MsoNormal”><FONT face=“Arial” color=“navy” size=“2”><SPAN style=“FONT-SIZE: 10pt;COLOR: navy;FONT-FAMILY: Arial;”>Best regards</SPAN></FONT></P>
<P class=“MsoNormal”><FONT face=“Arial” color=“navy” size=“2”><SPAN style=“FONT-SIZE: 10pt;COLOR: navy;FONT-FAMILY: Arial;”>Nirjhar Dhang</SPAN></FONT></P></DIV></FONT></DIV></FONT></DIV>
Hi Nirjhar
I recommend the following article on the problem of estimating rotations -
it introduces a method which minimises the errors in a least squares sense
of all markers in all time frames.
J. Lasenby, W. J. Fitzgerald, C. J. L. Doran and A. N. Lasenby.
New Geometric Methods for Computer Vision
Int. J. Comp. Vision 36(3), p. 191-213 (1998).
you can find it online (in postscript) at:
http://www.mrao.cam.ac.uk/~clifford/publications/abstracts/ijcv1_96.html
I think it should be best to minimise the number of steps between the raw
motion capture data and the AnyBody driver, since this will also allow to
perform an optimisation of the whole process rather than each separate bit.
good luck
Mark
On Wednesday, May 14, 2003 8:29 AM, Nirjhar Dhang [SMTP:nd@ime.auc.dk]
wrote:
> Dear AnyBody Users,
>
> My name is Nirjhar Dhang, and I am currently working in the AnyBody
> Research Group on development of an interface between the C3D file format
> and the AnyBody Modeling System. As you probably know, C3D is a standard
> file format for recording of movement data in gait analysis systems.
>
> The 3D marker points along with the EMG and force plate data are stored
in
> a binary formatted C3D file. Any Motion Capturing system, like VICON or
> QualiSYS has its own processing software, particularly for converting
> camera data for markers to 3D marker point data in the laboratory co-
> ordinate system. In the C3D file, each 3D marker point has a residual
> value which indicates the reliability of the data. The negative residual
> value indicates that the data is not acceptable, the positive value
> indicates the relative error and the zero value indicates that the data
> is computed rather than measured. Four popularly used marker sets are
> available for gait measurement. They are : a) Helen Hayes, b) Kit
> Vaughan, c) Cleveland Clinic and d) Mayo Clinic. In all these sets,
> fifteen markers are used. One more marker set is found in HIP98 CD
> distributed by the Free University of Berlin where 24 markers are used
> for measurement. However, only 15 land marks including joint centers are
> reported.
>
> It is for processing this type of data that we are developing the C3D
> interface. The ultimate goal of this work is to be able to read movement
> data from a C3D file and seamlessly create an AnyBody model that will
> model the gait movement and simulate the forces in the musculoskeletal
> system.
>
> Before we proceed we would like to hear the opinions you may have on the
> matter. The current status of the work is as follows:
>
> 1.A program called C3D2Any has been developed. It is invoked by
> the following command line
> C3D2Any <C3D file> <ANY | DAT file> [ANY | DAT ]
> The last argument in the above command line is optional. If the
> last argument is not given, the output file will be written in
AnyScript.
>
>
> 2.The program is prepared to have more features included for different
> output facilities, such as output of marker data only, or combination of
> marker data, EMG and force plate etc. This can be implemented by
> different command line arguments.
>
> 3.There is also a version available which builds upon the library
supplied
> by the C3D organization (www.c3d.org).
>
>
>
> Where are we going from here? Well, we need to solve a number of problems
> before the C3D file can directly produce a workable AnyScript model.
>
>
>
> a. The markers are attached on the surface of the body and errors are
> induced due to skin movement or by some other means. This introduces
> noise in the data. On the other hand, the data are redundant in the sense
> that we have more data than strictly necessary to identify the movement
> of each model segment in space. The problem is now how to process the
> noisy, redundant data to obtain joint centers. We have few ideas, but we
> would really appreciate your comments.
>
> b.Should we go for a solution that seamlessly converts the data to an
> AnyScript model in one step, or should we rather split the process into a
> few intermediate stages, for instance (1) filtering, (2) identification
> of the rigid body movement of each segment, (3) processing of the data to
> honor joint constraints. The advantage of having distinct steps is that
> it might enhance the user’s control of the process. What would you as
> users prefer?
>
>
>
> Please post your comments in the group. We really appreciate your help.
>
>
>
> Best regards
>
> Nirjhar Dhang
> << File: ATT00000.htm >>
One solution is to use another program to filter the data. I
recommend
filtering the noise while it’s still translation data. Filtering
rotational data is not a good idea. It will degrade the quality and
has some unpleasant results.
There are several solutions that can help with Marker labeling,
retargeting, and filtering the data with precision. Unfortunately the
software packages are a pretty penny but they do a fantastic job.
The first one is Kaydaras Motionbuilder. This is my first choice of
the two considering it has real-time feedback. The filtering tools
are really good and it’s available in Windows, Linux, and the Mac.
www.kaydara.com
The second is House of moves “Diva” www.moves.com. This package in my
opinion is the best for filtering noise, occlusions, gaps, and has
new retargeting functions. It also has it’s own scripting system.
Frank B.
— In anyscript@yahoogroups.com, Mark Thompson <mark.thompson@o…>
wrote:
> Hi Nirjhar
>
> I recommend the following article on the problem of estimating
rotations -
> it introduces a method which minimises the errors in a least
squares sense
> of all markers in all time frames.
>
> J. Lasenby, W. J. Fitzgerald, C. J. L. Doran and A. N. Lasenby.
> New Geometric Methods for Computer Vision
> Int. J. Comp. Vision 36(3), p. 191-213 (1998).
>
> you can find it online (in postscript) at:
>
http://www.mrao.cam.ac.uk/~clifford/publications/abstracts/ijcv1_96.ht
ml
>
> I think it should be best to minimise the number of steps between
the raw
> motion capture data and the AnyBody driver, since this will also
allow to
> perform an optimisation of the whole process rather than each
separate bit.
>
> good luck
>
> Mark
>
> On Wednesday, May 14, 2003 8:29 AM, Nirjhar Dhang [SMTP:nd@i…]
> wrote:
> > Dear AnyBody Users,
> >
> > My name is Nirjhar Dhang, and I am currently working in the
AnyBody
> > Research Group on development of an interface between the C3D
file format
> > and the AnyBody Modeling System. As you probably know, C3D is a
standard
> > file format for recording of movement data in gait analysis
systems.
> >
> > The 3D marker points along with the EMG and force plate data are
stored
> in
> > a binary formatted C3D file. Any Motion Capturing system, like
VICON or
> > QualiSYS has its own processing software, particularly for
converting
> > camera data for markers to 3D marker point data in the laboratory
co-
> > ordinate system. In the C3D file, each 3D marker point has a
residual
> > value which indicates the reliability of the data. The negative
residual
> > value indicates that the data is not acceptable, the positive
value
> > indicates the relative error and the zero value indicates that
the data
> > is computed rather than measured. Four popularly used marker sets
are
> > available for gait measurement. They are : a) Helen Hayes, b)
Kit
> > Vaughan, c) Cleveland Clinic and d) Mayo Clinic. In all these
sets,
> > fifteen markers are used. One more marker set is found in HIP98 CD
> > distributed by the Free University of Berlin where 24 markers are
used
> > for measurement. However, only 15 land marks including joint
centers are
> > reported.
> >
> > It is for processing this type of data that we are developing the
C3D
> > interface. The ultimate goal of this work is to be able to read
movement
> > data from a C3D file and seamlessly create an AnyBody model that
will
> > model the gait movement and simulate the forces in the
musculoskeletal
> > system.
> >
> > Before we proceed we would like to hear the opinions you may have
on the
> > matter. The current status of the work is as follows:
> >
> > 1.A program called C3D2Any has been developed. It is
invoked by
> > the following command line
> > C3D2Any <C3D file> <ANY | DAT file> [ANY | DAT ]
> > The last argument in the above command line is
optional. If the
> > last argument is not given, the output file will be
written in
> AnyScript.
> >
> >
> > 2.The program is prepared to have more features included for
different
> > output facilities, such as output of marker data only, or
combination of
> > marker data, EMG and force plate etc. This can be implemented by
> > different command line arguments.
> >
> > 3.There is also a version available which builds upon the library
> supplied
> > by the C3D organization (www.c3d.org).
> >
> >
> >
> > Where are we going from here? Well, we need to solve a number of
problems
> > before the C3D file can directly produce a workable AnyScript
model.
> >
> >
> >
> > a. The markers are attached on the surface of the body and errors
are
> > induced due to skin movement or by some other means. This
introduces
> > noise in the data. On the other hand, the data are redundant in
the sense
> > that we have more data than strictly necessary to identify the
movement
> > of each model segment in space. The problem is now how to process
the
> > noisy, redundant data to obtain joint centers. We have few ideas,
but we
> > would really appreciate your comments.
> >
> > b.Should we go for a solution that seamlessly converts the data
to an
> > AnyScript model in one step, or should we rather split the
process into a
> > few intermediate stages, for instance (1) filtering, (2)
identification
> > of the rigid body movement of each segment, (3) processing of the
data to
> > honor joint constraints. The advantage of having distinct steps
is that
> > it might enhance the user’s control of the process. What would
you as
> > users prefer?
> >
> >
> >
> > Please post your comments in the group. We really appreciate your
help.
> >
> >
> >
> > Best regards
> >
> > Nirjhar Dhang
> > << File: ATT00000.htm >>
<table border=0 cellpadding=2 cellspacing=“0”><tr><td><!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.0 Transitional//EN”>
<DIV><FONT face=“Arial” size=“2”>Gait Driver : AnyBody interface</FONT></DIV>
<DIV><FONT face=“Arial” size=“2”></FONT></DIV>
<DIV><FONT face=“Arial” size=“2”>Different steps required for gait analysis areas follows :</FONT></DIV>
<DIV><FONT face=“Arial” size=“2”>
- Laboratory part
a) placement of camera,
b) calibration of camera,
c) zeroing of force platform
d) attachment of markers
e) attachment of EMG electrodes
f) Static trials
g) dynamic trials - gait measurement</font></DIV>
<DIV></DIV>
<DIV>2. Processing of data
a) filtering noise, b) gap filling </DIV>
<DIV></DIV>
<DIV>3. Analysis
a) Kinematic analysis
b) Inverse dynamics</DIV>
<DIV></DIV>
<DIV>
We are assuming first two steps can be done by any motion measurement system. After preliminary processing of marker and analog data, it will be delivered as C3D format, usual mode of representing motion data.For the time being, we would like to start from here.</DIV>
<DIV></DIV>
<DIV>The popular marker sets for gait measurement are : a) Helen Hayes, b) Kit Vaughan, c) Cleveland Clinic and d) Mayo Clinic. </DIV>
<DIV></DIV>
<DIV>Now let me put the problem once more :</DIV>
<DIV></DIV>
<DIV>Each marker set as mentioned above uses 15 markers attached on the surface on the body. Typically, say, 100 frames are acquired. A 3D gait model is already developed considering the lower extremity, now a driver is needed based on marker data.
</DIV>
<DIV>Now, it appears we have the following two options :</DIV>
<DIV></DIV>
<DIV>1) Compute joint centers, such as, hip joint center (HJC), knee joint center(KJC) and ankle joint center(AJC) from the marker data and prescribe motion by angles, angular velocity and acceleration.</DIV>
<DIV></DIV>
<DIV>2) Provide orientation of rigid segments and position, velocity and acceleration of atleast one point of each rigid segment
</DIV>
<DIV>Which one is preferrable?</DIV>
<DIV></DIV>
<DIV>It will be helpful, if you post your option with explanation.</DIV>
<DIV></DIV>
<DIV>Nirjhar</DIV>
<DIV></DIV>
<DIV>
</DIV>
<DIV><FONT face=“Arial” size=“2”></FONT></DIV>
<BLOCKQUOTE style=“BORDER-LEFT: #000000 2px solid;”>
<DIV style=“FONT: 10pt arial;”>----- Original Message ----- </DIV>
<DIV style=“BACKGROUND: #e4e4e4;FONT: 10pt arial;”>From: fbonniwell </DIV>
<DIV style=“FONT: 10pt arial;”>To: anyscript@yahoogroups.com </DIV>
<DIV style=“FONT: 10pt arial;”>Sent: Monday, May 26, 2003 2:33 AM</DIV>
<DIV style=“FONT: 10pt arial;”>Subject: [anyscript] Re: C3D - AnyBody Interface - seeking your comments</DIV>
<DIV><FONT face=“Arial” size=“2”></FONT><FONT face=“Arial” size=“2”></FONT>
</DIV><TT>
One solution is to use another program to filter the data. I
recommend
filtering the noise while it’s still translation data. Filtering
rotational data is not a good idea. It will degrade the quality and
has some unpleasant results.
There are several solutions that can help with Marker labeling,
retargeting, and filtering the data with precision. Unfortunately the
software packages are a pretty penny but they do a fantastic job.
The first one is Kaydaras Motionbuilder. This is my first choice of
the two considering it has real-time feedback. The filtering tools
are really good and it’s available in Windows, Linux, and the Mac.
www.kaydara.com
The second is House of moves “Diva” www.moves.com. This package in my
opinion is the best for filtering noise, occlusions, gaps, and has
new retargeting functions. It also has it’s own scripting system.
Frank B.
— In anyscript@yahoogroups.com, Mark Thompson <mark.thompson@o…>
wrote:
> Hi Nirjhar
>
> I recommend the following article on the problem of estimating
rotations -
> it introduces a method which minimises the errors in a least
squares sense
> of all markers in all time frames.
>
> J. Lasenby, W. J. Fitzgerald, C. J. L. Doran and A. N. Lasenby.
> New Geometric Methods for Computer Vision
> Int. J. Comp. Vision 36(3), p. 191-213 (1998).
>
> you can find it online (in postscript) at:
>
http://www.mrao.cam.ac.uk/~clifford/publications/abstracts/ijcv1_96.ht
ml
>
> I think it should be best to minimise the number of steps between
the raw
> motion capture data and the AnyBody driver, since this will also
allow to
> perform an optimisation of the whole process rather than each
separate bit.
>
> good luck
>
> Mark
>
> On Wednesday, May 14, 2003 8:29 AM, Nirjhar Dhang [SMTP:nd@i…]
> wrote:
> > Dear AnyBody Users,
> >
> > My name is Nirjhar Dhang, and I am currently working in the
AnyBody
> > Research Group on development of an interface between the C3D
file format
> > and the AnyBody Modeling System. As you probably know, C3D is a
standard
> > file format for recording of movement data in gait analysis
systems.
> >
> > The 3D marker points along with the EMG and force plate data are
stored
> in
> > a binary formatted C3D file. Any Motion Capturing system, like
VICON or
> > QualiSYS has its own processing software, particularly for
converting
> > camera data for markers to 3D marker point data in the laboratory
co-
> > ordinate system. In the C3D file, each 3D marker point has a
residual
> > value which indicates the reliability of the data. The negative
residual
> > value indicates that the data is not acceptable, the positive
value
> > indicates the relative error and the zero value indicates that
the data
> > is computed rather than measured. Four popularly used marker sets
are
> > available for gait measurement. They are : a) Helen Hayes, b)
Kit
> > Vaughan, c) Cleveland Clinic and d) Mayo Clinic. In all these
sets,
> > fifteen markers are used. One more marker set is found in HIP98 CD
> > distributed by the Free University of Berlin where 24 markers are
used
> > for measurement. However, only 15 land marks including joint
centers are
> > reported.
> >
> > It is for processing this type of data that we are developing the
C3D
> > interface. The ultimate goal of this work is to be able to read
movement
> > data from a C3D file and seamlessly create an AnyBody model that
will
> > model the gait movement and simulate the forces in the
musculoskeletal
> > system.
> >
> > Before we proceed we would like to hear the opinions you may have
on the
> > matter. The current status of the work is as follows:
> >
> > 1.A program called C3D2Any has been developed. It is
invoked by
> > the following command line
> > C3D2Any <C3D file> <ANY | DAT file> [ANY | DAT ]
> > The last argument in the above command line is
optional. If the
> > last argument is not given, the output file will be
written in
> AnyScript.
> >
> >
> > 2.The program is prepared to have more features included for
different
> > output facilities, such as output of marker data only, or
combination of
> > marker data, EMG and force plate etc. This can be implemented by
> > different command line arguments.
> >
> > 3.There is also a version available which builds upon the library
> supplied
> > by the C3D organization (www.c3d.org).
> >
> >
> >
> > Where are we going from here? Well, we need to solve a number of
problems
> > before the C3D file can directly produce a workable AnyScript
model.
> >
> >
> >
> > a. The markers are attached on the surface of the body and errors
are
> > induced due to skin movement or by some other means. This
introduces
> > noise in the data. On the other hand, the data are redundant in
the sense
> > that we have more data than strictly necessary to identify the
movement
> > of each model segment in space. The problem is now how to process
the
> > noisy, redundant data to obtain joint centers. We have few ideas,
but we
> > would really appreciate your comments.
> >
> > b.Should we go for a solution that seamlessly converts the data
to an
> > AnyScript model in one step, or should we rather split the
process into a
> > few intermediate stages, for instance (1) filtering, (2)
identification
> > of the rigid body movement of each segment, (3) processing of the
data to
> > honor joint constraints. The advantage of having distinct steps
is that
> > it might enhance the user’s control of the process. What would
you as
> > users prefer?
> >
> >
> >
> > Please post your comments in the group. We really appreciate your
help.
> >
> >
> >
> > Best regards
> >
> > Nirjhar Dhang
> > << File: ATT00000.htm >>
</TT>
<TT>To unsubscribe from this group, send an email to:
anyscript-unsubscribe@yahoogroups.com
</TT>
<TT>Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.</TT>
</BLOCKQUOTE>