AnyInt - AnyFloat?

Hi all,

I am trying to convert a model built on the previous version to the
current one. I have gotten stuck on this one thing and do not know how
to proceed. When I read the code in I get the message:

Evaluating constants…
ERROR(SCR.EXP1) : C:\Program Files\AnyBody
Technology\AnyBody.2.0\Repository.5\ARep\Aalborg\Patient 2
FootApp_Wedge_Right\MarkerMover.any(37) : ‘=’ : Illegal operation
for given argument types : ‘AnyInt’ ‘=’ ‘AnyFloat’

This is surely not a problem with the source data?

Thanks for any help you can provide.

Cheers,

-Jari

Hi Jari,

I have too little to go at…

There are some functions that can be used to convert floats to ints,
such as round(float), ceil(float), floor(int).

But you somehow indicate that it has nothing to do with the input.

About the conversion you are doing. There are a couple of things
which are not compatible between the preview and final release 2.0
editions. The major ones are:

  1. Initial positions in the segment are now given by ‘r0’
    and ‘Axes0’ instead of ‘r’ and ‘Axes’. (This you probably have found
    already.)

  2. Some scope resolving have changes so you might to change the
    preceeding number of ‘.’ in relative names

  3. Some floats and integers have been changed to integers or enum in
    some cases, such as the Reaction.Type member in kinematic
    constraints. These are cases where some variable was introduced in
    old versions of AnyBody before as many data types were available. We
    are using the Major updates to clean out some of these cases.
    Maybe you have encountered such as case, maybe you just need to
    change 1.0 to 1. Could this be the case?

If not, could you send me some additional information about your
specific case, then I may be able to be more specific?
Or you could upload your entire model, so I could have a look.

Best regards,

Michael
AnyBody Support

— In anyscript@yahoogroups.com, “jari4455” <j.pallari@…> wrote:
>
>
> Hi all,
>
> I am trying to convert a model built on the previous version to
the
> current one. I have gotten stuck on this one thing and do not know
how
> to proceed. When I read the code in I get the message:
>
> Evaluating constants…
> ERROR(SCR.EXP1) : C:\Program Files\AnyBody
> Technology\AnyBody.2.0\Repository.5\ARep\Aalborg\Patient 2
> FootApp_Wedge_Right\MarkerMover.any(37) : ‘=’ : Illegal
operation
> for given argument types : ‘AnyInt’ ‘=’ ‘AnyFloat’
>
> This is surely not a problem with the source data?
>
> Thanks for any help you can provide.
>
> Cheers,
>
> -Jari
>

Hi Michael,

Thanks for the advice.

  1. I did notice. I only wish that the other fixes would be as easy.

  2. I did try this up to four .'s. No luck.

  3. Trust me, you do not want to see the whole thing :slight_smile:

I’m not entirely sure I understand what you mean. Should I change all of the
1’s to 1.0’s when describing kinematic constraints? I have not tried this, since
there are quite a few of them.

The error message is referring to the markermover file, which is the same as
in the original gait analysis model. The specific line is “BsplineOrder =
8.000000;”, in this context:

AnyKinEqInterPolDriver LinDrv={
AnyKinLinear &ref1= .Lin;
//Type=PiecewiseLinear;
//Type=Bezier;
Type=Bspline;
BsplineOrder = 8.000000;
FileName =.datafile;//reference to the name of the data file to use
};

I can send the whole markermover.any if that helps.

Thanks,

-Jari

AnyBody Support <support@anybodytech.com> wrote:
Hi Jari,

I have too little to go at…

There are some functions that can be used to convert floats to ints,
such as round(float), ceil(float), floor(int).

But you somehow indicate that it has nothing to do with the input.

About the conversion you are doing. There are a couple of things
which are not compatible between the preview and final release 2.0
editions. The major ones are:

  1. Initial positions in the segment are now given by ‘r0’
    and ‘Axes0’ instead of ‘r’ and ‘Axes’. (This you probably have found
    already.)

  2. Some scope resolving have changes so you might to change the
    preceeding number of ‘.’ in relative names

  3. Some floats and integers have been changed to integers or enum in
    some cases, such as the Reaction.Type member in kinematic
    constraints. These are cases where some variable was introduced in
    old versions of AnyBody before as many data types were available. We
    are using the Major updates to clean out some of these cases.
    Maybe you have encountered such as case, maybe you just need to
    change 1.0 to 1. Could this be the case?

If not, could you send me some additional information about your
specific case, then I may be able to be more specific?
Or you could upload your entire model, so I could have a look.

Best regards,

Michael
AnyBody Support

— In anyscript@yahoogroups.com, “jari4455” <j.pallari@…> wrote:
>
>
> Hi all,
>
> I am trying to convert a model built on the previous version to
the
> current one. I have gotten stuck on this one thing and do not know
how
> to proceed. When I read the code in I get the message:
>
> Evaluating constants…
> ERROR(SCR.EXP1) : C:\Program Files\AnyBody
> Technology\AnyBody.2.0\Repository.5\ARep\Aalborg\Patient 2
> FootApp_Wedge_Right\MarkerMover.any(37) : ‘=’ : Illegal
operation
> for given argument types : ‘AnyInt’ ‘=’ ‘AnyFloat’
>
> This is surely not a problem with the source data?
>
> Thanks for any help you can provide.
>
> Cheers,
>
> -Jari
>

[Non-text portions of this message have been removed]

Hi Jari,

Try BsplineOrder = 8;

BsplineOrder was previously an AnyFloat (dating back to the days
before AnyInt). All the ‘.000’ probably came from the Class Template
Inserter Tool, since it treated it as a float, not knowing that we
intended it to be an integer.
But now it is a real integer.

If you get anymore of these, try removing zeros behind the ‘.’.
If there is something else than zeros behind the point, then worry
more, otherwise it is just a syntactical issue due to the update.

Thanks for not showing me everything :wink:

Michael
AnyBody Support

— In anyscript@yahoogroups.com, JARI PALLARI <j.pallari@…> wrote:
>
> Hi Michael,
>
> Thanks for the advice.
>
> 1. I did notice. I only wish that the other fixes would be as
easy.
>
> 2. I did try this up to four .'s. No luck.
>
> 3. Trust me, you do not want to see the whole thing :slight_smile:
>
> I’m not entirely sure I understand what you mean. Should I
change all of the 1’s to 1.0’s when describing kinematic
constraints? I have not tried this, since there are quite a few of
them.
>
> The error message is referring to the markermover file, which is
the same as in the original gait analysis model. The specific line
is “BsplineOrder = 8.000000;”, in this context:
>
> AnyKinEqInterPolDriver LinDrv={
> AnyKinLinear &ref1= .Lin;
> //Type=PiecewiseLinear;
> //Type=Bezier;
> Type=Bspline;
> BsplineOrder = 8.000000;
> FileName =.datafile;//reference to the name of the data file to
use
> };
>
> I can send the whole markermover.any if that helps.
>
> Thanks,
>
> -Jari
>
>
> AnyBody Support <support@…> wrote:
> Hi Jari,
>
> I have too little to go at…
>
> There are some functions that can be used to convert floats to
ints,
> such as round(float), ceil(float), floor(int).
>
> But you somehow indicate that it has nothing to do with the input.
>
> About the conversion you are doing. There are a couple of things
> which are not compatible between the preview and final release 2.0
> editions. The major ones are:
>
> 1) Initial positions in the segment are now given by ‘r0’
> and ‘Axes0’ instead of ‘r’ and ‘Axes’. (This you probably have
found
> already.)
>
> 2) Some scope resolving have changes so you might to change the
> preceeding number of ‘.’ in relative names
>
> 3) Some floats and integers have been changed to integers or enum
in
> some cases, such as the Reaction.Type member in kinematic
> constraints. These are cases where some variable was introduced in
> old versions of AnyBody before as many data types were available.
We
> are using the Major updates to clean out some of these cases.
> Maybe you have encountered such as case, maybe you just need to
> change 1.0 to 1. Could this be the case?
>
> If not, could you send me some additional information about your
> specific case, then I may be able to be more specific?
> Or you could upload your entire model, so I could have a look.
>
> Best regards,
>
> Michael
> AnyBody Support
>
> — In anyscript@yahoogroups.com, “jari4455” <j.pallari@> wrote:
> >
> >
> > Hi all,
> >
> > I am trying to convert a model built on the previous version to
> the
> > current one. I have gotten stuck on this one thing and do not
know
> how
> > to proceed. When I read the code in I get the message:
> >
> > Evaluating constants…
> > ERROR(SCR.EXP1) : C:\Program Files\AnyBody
> > Technology\AnyBody.2.0\Repository.5\ARep\Aalborg\Patient 2
> > FootApp_Wedge_Right\MarkerMover.any(37) : ‘=’ : Illegal
> operation
> > for given argument types : ‘AnyInt’ ‘=’ ‘AnyFloat’
> >
> > This is surely not a problem with the source data?
> >
> > Thanks for any help you can provide.
> >
> > Cheers,
> >
> > -Jari
> >
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

Howdy,

It now runs! Many thanks,

-Jari

AnyBody Support <support@anybodytech.com> wrote:
Hi Jari,

Try BsplineOrder = 8;

BsplineOrder was previously an AnyFloat (dating back to the days
before AnyInt). All the ‘.000’ probably came from the Class Template
Inserter Tool, since it treated it as a float, not knowing that we
intended it to be an integer.
But now it is a real integer.

If you get anymore of these, try removing zeros behind the ‘.’.
If there is something else than zeros behind the point, then worry
more, otherwise it is just a syntactical issue due to the update.

Thanks for not showing me everything :wink:

Michael
AnyBody Support

— In anyscript@yahoogroups.com, JARI PALLARI <j.pallari@…> wrote:
>
> Hi Michael,
>
> Thanks for the advice.
>
> 1. I did notice. I only wish that the other fixes would be as
easy.
>
> 2. I did try this up to four .'s. No luck.
>
> 3. Trust me, you do not want to see the whole thing :slight_smile:
>
> I’m not entirely sure I understand what you mean. Should I
change all of the 1’s to 1.0’s when describing kinematic
constraints? I have not tried this, since there are quite a few of
them.
>
> The error message is referring to the markermover file, which is
the same as in the original gait analysis model. The specific line
is “BsplineOrder = 8.000000;”, in this context:
>
> AnyKinEqInterPolDriver LinDrv={
> AnyKinLinear &ref1= .Lin;
> //Type=PiecewiseLinear;
> //Type=Bezier;
> Type=Bspline;
> BsplineOrder = 8.000000;
> FileName =.datafile;//reference to the name of the data file to
use
> };
>
> I can send the whole markermover.any if that helps.
>
> Thanks,
>
> -Jari
>
>
> AnyBody Support <support@…> wrote:
> Hi Jari,
>
> I have too little to go at…
>
> There are some functions that can be used to convert floats to
ints,
> such as round(float), ceil(float), floor(int).
>
> But you somehow indicate that it has nothing to do with the input.
>
> About the conversion you are doing. There are a couple of things
> which are not compatible between the preview and final release 2.0
> editions. The major ones are:
>
> 1) Initial positions in the segment are now given by ‘r0’
> and ‘Axes0’ instead of ‘r’ and ‘Axes’. (This you probably have
found
> already.)
>
> 2) Some scope resolving have changes so you might to change the
> preceeding number of ‘.’ in relative names
>
> 3) Some floats and integers have been changed to integers or enum
in
> some cases, such as the Reaction.Type member in kinematic
> constraints. These are cases where some variable was introduced in
> old versions of AnyBody before as many data types were available.
We
> are using the Major updates to clean out some of these cases.
> Maybe you have encountered such as case, maybe you just need to
> change 1.0 to 1. Could this be the case?
>
> If not, could you send me some additional information about your
> specific case, then I may be able to be more specific?
> Or you could upload your entire model, so I could have a look.
>
> Best regards,
>
> Michael
> AnyBody Support
>
> — In anyscript@yahoogroups.com, “jari4455” <j.pallari@> wrote:
> >
> >
> > Hi all,
> >
> > I am trying to convert a model built on the previous version to
> the
> > current one. I have gotten stuck on this one thing and do not
know
> how
> > to proceed. When I read the code in I get the message:
> >
> > Evaluating constants…
> > ERROR(SCR.EXP1) : C:\Program Files\AnyBody
> > Technology\AnyBody.2.0\Repository.5\ARep\Aalborg\Patient 2
> > FootApp_Wedge_Right\MarkerMover.any(37) : ‘=’ : Illegal
> operation
> > for given argument types : ‘AnyInt’ ‘=’ ‘AnyFloat’
> >
> > This is surely not a problem with the source data?
> >
> > Thanks for any help you can provide.
> >
> > Cheers,
> >
> > -Jari
> >
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

[Non-text portions of this message have been removed]