The Altair Community is migrating to a new platform to provide a better experience for you. In preparation for the migration, the Altair Community is on read-only mode from October 28 - November 6, 2024. Technical support via cases will continue to work as is. For any urgent requests from Students/Faculty members, please submit the form linked here

new role, meta data!

wesselwessel Member Posts: 537 Maven
edited June 2019 in Help
Often I have some attributes which are only used to check if everything goes as planned.
So they should not be used by the learner.
To prevent the learner from using these attributes you can change the role to ID or batch or cluster,
but this is not really the intended purpose of the the change role operator.

Would be nice to have a roll "meta" which indicates this attribute should not be used, but should not be thrown away either.

Best regards,

Wessel

Answers

  • fischerfischer Member Posts: 439 Maven
    Hi,

    actually, I typically just set the role to "ignored" (not that you can use arbitrary strings as role names). This way, you make sure that you don't confuse any operator by using a defined role. Still, it may be worth to introduce such an "ignored" role as a standard role name.

    Cheers,
    Simon
  • wesselwessel Member Posts: 537 Maven
    Hmm, the problem is, when I use the operator "windowing", the only special attribute that remains after windowing is 'id', all others are removed for some reason.
  • fischerfischer Member Posts: 439 Maven
    Which "windowing" operator are you referring to?
  • wesselwessel Member Posts: 537 Maven
    The operator is called "windowing" so not "windowing (series)"
Sign In or Register to comment.