[akutuva21]

What (issue addressed):
The previous implementation of set_species_init and set_parameters in CSimWrapper (bionetgen/simulator/csimulator.py) used simple assert statements to check if the lengths of the passed arrays matched num_spec_init and num_params respectively. These asserts caused hard-to-debug crashes (AssertionError) and were documented with a TODO: Transition to BNGErrors and logging.

Why (maintainability improvement):
Transitioning to explicit checks that raise custom exceptions (BNGSimulatorError) and write precise runtime context to the standardized BNGLogger dramatically improves debugging. The app will now safely catch setup mismatches rather than unexpectedly failing due to standard assertion behaviors which get optimized out when running Python in optimized mode (-O).

Verification (how it was confirmed safe):

• Introduced the BNGSimulatorError subclass to bionetgen/core/exc.py.
• Replaced the assert lines with conditional block utilizing self.logger.error and raise BNGSimulatorError in bionetgen/simulator/csimulator.py.
• Verified logic safety by isolating the unit block tests and using unittest.mock.patch on ctypes.CDLL to ensure the exceptions correctly bubble up with accurate information without side effects.
• Tested and ran successfully using isolated pytest sessions.

Result:
The PyBioNetGen simulator framework correctly handles argument shape mismatch issues gracefully, fulfilling the explicit TODO and standardizing error handling across the application.

---

PR created automatically by Jules for task 140854119988854650 started by @akutuva21

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.