You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I create a life phase using create_life_phase(), I set the duration to 500 hours. This value is based on multiplying the number of cycles in the thermal event by the duration of the corresponding thermal profile i want to load into the event. However, when I try to add the thermal event, I receive the following error:
ERROR - lifecycle - add_thermal_event - Add thermal event error: Duration must be no greater than the cycle time period (1.0 hr)
I believe this error occurs because a default profile with a duration of 2.33 hours is automatically loaded when the thermal event is created. When multiplied by the 500 cycles, this exceeds the initially set duration of the life phase, resulting in the error.
Is there a way to modify the default profile that gets loaded? If not, could a function be added to allow users to update the properties of a life phase after creation? This would allow setting a higher duration for the life phase initially, which could then be adjusted once the correct profile is loaded.
sherlock.lifecycle.load_thermal_profile(
project="test",
phase_name="phase",
event_name="event",
file_path="profile.dat", # Thermal profile has a duration of 1 hour
)
🔍 Before submitting the issue
🐞 Description of the bug
When I create a life phase using create_life_phase(), I set the duration to 500 hours. This value is based on multiplying the number of cycles in the thermal event by the duration of the corresponding thermal profile i want to load into the event. However, when I try to add the thermal event, I receive the following error:
ERROR - lifecycle - add_thermal_event - Add thermal event error: Duration must be no greater than the cycle time period (1.0 hr)
I believe this error occurs because a default profile with a duration of 2.33 hours is automatically loaded when the thermal event is created. When multiplied by the 500 cycles, this exceeds the initially set duration of the life phase, resulting in the error.
Is there a way to modify the default profile that gets loaded? If not, could a function be added to allow users to update the properties of a life phase after creation? This would allow setting a higher duration for the life phase initially, which could then be adjusted once the correct profile is loaded.
📝 Steps to reproduce
sherlock.lifecycle.create_life_phase(
project="test",
phase_name="phase",
duration=500,
duration_units="hr",
num_of_cycles=1,
cycle_type="COUNT",
)
This funciton will trigger the error message
sherlock.lifecycle.add_thermal_event(
project="test",
phase_name="phase",
event_name = "event",
num_of_cycles=500,
cycle_type="COUNT",
cycle_state="OPERATING",
)
sherlock.lifecycle.load_thermal_profile(
project="test",
phase_name="phase",
event_name="event",
file_path="profile.dat", # Thermal profile has a duration of 1 hour
)
💻 Which operating system are you using?
Windows
📀 Which ANSYS version are you using?
2024R2
🐍 Which Python version are you using?
3.9
📦 Installed packages
ansys-api-sherlock==0.1.31
ansys-dpf-core==0.9.0
ansys-dpf-gate==0.4.1
ansys-dpf-gatebin==0.4.1
ansys-dpf-post==0.5.0
ansys-grpc-dpf==0.8.1
ansys-sherlock-core==0.7.1
cachetools==5.5.0
certifi==2024.8.30
charset-normalizer==3.4.0
colorama==0.4.6
customtkinter==5.2.2
darkdetect==0.8.0
et-xmlfile==1.1.0
google-api-core==2.22.0
google-api-python-client==2.149.0
google-auth==2.35.0
google-auth-httplib2==0.2.0
googleapis-common-protos==1.65.0
grpcio==1.66.1
grpcio-tools==1.66.1
httplib2==0.22.0
idna==3.10
importlib_metadata==8.4.0
numpy==1.24.4
openpyxl==3.1.5
packaging==24.1
pandas==2.0.3
pillow==10.4.0
proto-plus==1.25.0
protobuf==5.28.0
psutil==6.1.0
pyasn1==0.6.1
pyasn1_modules==0.4.1
pyparsing==3.1.4
python-dateutil==2.9.0.post0
pytz==2024.2
pywin32==308
requests==2.32.3
rsa==4.9
scooby==0.10.0
six==1.16.0
tk==0.1.0
tqdm==4.66.6
tzdata==2024.1
uritemplate==4.1.1
urllib3==2.2.3
zipp==3.20.1
The text was updated successfully, but these errors were encountered: