ThrusterStateEffector / ThrusterDynamicEffector attribute `thrusterData` is not wrapped

[atharris-ts]

Describe the bug
Something is broken in how both thruster module's thrusterData attribute is swig'd.

To reproduce
Steps to reproduce the behavior:

1. Open scenarioOrbitManeuverTH.py. On line 328, add print(thrusterSet.thrusterData[0]).
2. Run scenarioOrbitManeuverTH.py.
3. Observe `*** TypeError: 'SwigPyObject' object is not subscriptable

Expected behavior
ThrusterStateEffector and ThrusterDynamicEffector should allow users to access their thrusterData members as iterable lists in Python.

Desktop (please complete the following information):

• OS: Ubuntu 22.04
• Version: Pulled from develop, commit dbf5237
• Python version: 3.10.12

Additional context
I didn't see anything obviously wrong in the swig files for either thruster module - I have code that was using this based on an older basilisk version from ~mid 2025.

[atharris]

Weird bug, but I did find a workaround by explicitly scripting the getter behavior in the swig files for both thruster types. For thrusterStateEffector.i, this looks like:

/*
 ISC License

 Copyright (c) 2022, Autonomous Vehicle Systems Lab, University of Colorado at Boulder

 Permission to use, copy, modify, and/or distribute this software for any
 purpose with or without fee is hereby granted, provided that the above
 copyright notice and this permission notice appear in all copies.

 THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
 WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
 MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
 ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
 WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
 ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

 */


%module thrusterStateEffector

%include "architecture/utilities/bskException.swg"
%default_bsk_exception();

%{
   #include "thrusterStateEffector.h"
%}

%pythoncode %{
from Basilisk.architecture.swig_common_model import *
%}

%include "std_string.i"
%include "swig_eigen.i"
%include "swig_conly_data.i"

%include "sys_model.i"
%include "simulation/dynamics/_GeneralModuleFiles/dynParamManager.i"
%include "simulation/dynamics/_GeneralModuleFiles/stateEffector.h"
%import "simulation/dynamics/_GeneralModuleFiles/THRSimConfig.i"
%include "thrusterStateEffector.h"

namespace std {
    %template(ThrusterDataVector) vector<std::shared_ptr<THRSimConfig>>;
}

%include "architecture/msgPayloadDefC/THRArrayOnTimeCmdMsgPayload.h"
struct THRArrayOnTimeCmdMsg_C;
%include "architecture/msgPayloadDefCpp/THROutputMsgPayload.h"
%include "architecture/msgPayloadDefC/SCStatesMsgPayload.h"
struct SCStatesMsg_C;

%pythoncode %{
from Basilisk.simulation.THRSimConfig import THRSimConfig as THRSimConfig
%}

%pythoncode %{
def _ThrusterDataVector_getitem(self, index):
    n = len(self)
    if isinstance(index, slice):
        return [list(self)[i] for i in range(*index.indices(n))]
    if index < 0:
        index += n
    if index < 0 or index >= n:
        raise IndexError("index out of range")
    for i, item in enumerate(self):
        if i == index:
            return item
ThrusterDataVector.__getitem__ = _ThrusterDataVector_getitem
%}

%pythoncode %{
import sys
protectAllClasses(sys.modules[__name__])
%}

Recompiling with this seems to fix the issue. I can put together a PR for this, @schaubh what's the process for actually making a contribution?

[schaubh]

@juan-g-bonilla , if you have a moment, please take a look at this swig issue. Can you think of a more general solution rather than having to write this explicit getter in the swig file?