[X] Yes, I have updated AB and still experience this issue
What happened?
I encountered something that is very weird…
I cannot even properly reconstruct it, but it must have to do with the installation of a database going into a new thread or so.
I did a scenario LCA, for which the AB realized that it had to do some relinking (i.e. in the scenario file I pointed to a superstructure database, which I don’t have right now, so I re-linked it to ecoinvent 3.9.1). It calculated the scenario LCA alright.
But then, it also installed new database (!!). It looks like ecoinvent 3.9.1, but without a name. I do not recall it asking for it. But at some point I noticed that the relinking also opened not only one relinking dialogue, but a set of dialogues in parallel, which seemed to have been in a parallel thread. In the end I have this db now – very strange.
@Zoophobus, I know this is a terrible description, but could you try importing the attached file against ecoinvent 3.9.1. and see if you get something similar?
Relevant errors
Loading Scenario file. This may take a while for large files
C:\Users\steub\miniconda3\envs\ab\lib\site-packages\activity_browser\bwutils\superstructure\excel.py:86: FutureWarning: DataFrame.applymap has been deprecated. Use DataFrame.map instead.
data.loc[:, columns] = data[columns].applymap(convert_tuple_str)
Traceback (most recent call last):
File "C:\Users\steub\miniconda3\envs\ab\lib\site-packages\activity_browser\ui\tables\delegates\checkbox.py", line 22, in paint
painter.save()
AttributeError: 'PySide2.QtGui.QResizeEvent' object has no attribute 'save'
Traceback (most recent call last):
File "C:\Users\steub\miniconda3\envs\ab\lib\site-packages\activity_browser\ui\tables\delegates\checkbox.py", line 22, in paint
painter.save()
AttributeError: 'PySide2.QtGui.QResizeEvent' object has no attribute 'save'
Traceback (most recent call last):
File "C:\Users\steub\miniconda3\envs\ab\lib\site-packages\activity_browser\ui\tables\delegates\checkbox.py", line 22, in paint
painter.save()
AttributeError: 'PySide2.QtGui.QResizeEvent' object has no attribute 'save'
Traceback (most recent call last):
File "C:\Users\steub\miniconda3\envs\ab\lib\site-packages\activity_browser\ui\tables\delegates\checkbox.py", line 22, in paint
painter.save()
AttributeError: 'PySide2.QtGui.QResizeEvent' object has no attribute 'save'
Traceback (most recent call last):
File "C:\Users\steub\miniconda3\envs\ab\lib\site-packages\activity_browser\ui\tables\delegates\checkbox.py", line 22, in paint
painter.save()
AttributeError: 'PySide2.QtGui.QResizeEvent' object has no attribute 'save'
Traceback (most recent call last):
File "C:\Users\steub\miniconda3\envs\ab\lib\site-packages\activity_browser\ui\tables\delegates\checkbox.py", line 22, in paint
painter.save()
AttributeError: 'PySide2.QtGui.QResizeEvent' object has no attribute 'save'
C:\Users\steub\miniconda3\envs\ab\lib\site-packages\activity_browser\bwutils\superstructure\dataframe.py:142: FutureWarning: Series.__getitem__ treating keys as positions is deprecated. In a future version, integer keys will always be treated as labels (consistent with DataFrame behavior). To access a value by position, use `ser.iloc[pos]`
ds_.loc[col] = (key['database'][0], key['code'][0]) if j == 0 else key['database'][0]
1.0<function ScenarioImportWidget.scenario_db_check at 0x000002363CEB7EE0> -- 3.3886168003082275
<function SuperstructureManager.fill_empty_process_keys_in_exchanges at 0x00000236383115E0> -- 0.0
<function SuperstructureManager.verify_scenario_process_keys at 0x0000023638311700> -- 0.009251594543457031
<function SuperstructureManager.check_duplicates at 0x0000023638311940> -- 0.0010173320770263672
<function SuperstructureManager.check_scenario_exchange_values at 0x0000023638311820> -- 0.001001119613647461
<function SuperstructureManager.merge_flows_to_self at 0x0000023638311310> -- 0.005011320114135742
<function ScenarioImportWidget.sync_superstructure at 0x000002363CEB7DC0> -- 3.4768824577331543
<function ScenarioImportWidget.load_action at 0x000002363CEB7CA0> -- 9.98945951461792
+showing tab:LCA results
Extracted 21238 datasets in 398.75 seconds
Applying strategy: normalize_units
Applying strategy: update_ecoinvent_locations
Applying strategy: remove_zero_amount_coproducts
Applying strategy: remove_zero_amount_inputs_with_no_activity
Applying strategy: remove_unnamed_parameters
Applying strategy: es2_assign_only_product_with_amount_as_reference_product
Applying strategy: assign_single_product_as_activity
Applying strategy: create_composite_code
Applying strategy: drop_unspecified_subcategories
Applying strategy: fix_ecoinvent_flows_pre35
Applying strategy: drop_temporary_outdated_biosphere_flows
Applying strategy: link_biosphere_by_flow_uuid
Applying strategy: link_internal_technosphere_by_composite_code
Applying strategy: delete_exchanges_missing_activity
Applying strategy: delete_ghost_exchanges
Applying strategy: remove_uncertainty_from_negative_loss_exchanges
Applying strategy: fix_unreasonably_high_lognormal_uncertainties
Applying strategy: convert_activity_parameters_to_list
Applying strategy: add_cpc_classification_from_single_reference_product
Applying strategy: delete_none_synonyms
Applying strategy: set_lognormal_loc_value
Applied 21 strategies in 9.21 seconds
Writing activities to SQLite3 database:
0% [##############################] 100% | ETA: 00:00:00
Total time elapsed: 00:00:56
Title: Writing activities to SQLite3 database:
Started: 10/13/2023 17:29:55
Finished: 10/13/2023 17:30:52
Total time elapsed: 00:00:56
CPU %: 100.20
Memory %: 13.49
Created database:
Reset project settings directory to:C:\Users\steub\OneDrive - Universiteit Leiden\Brightway3\ei391.d59e0d309e8ebcc899228a6029307b93
Updating AB
What happened?
I encountered something that is very weird…
I cannot even properly reconstruct it, but it must have to do with the installation of a database going into a new thread or so.
I did a scenario LCA, for which the AB realized that it had to do some relinking (i.e. in the scenario file I pointed to a superstructure database, which I don’t have right now, so I re-linked it to ecoinvent 3.9.1). It calculated the scenario LCA alright.
But then, it also installed new database (!!). It looks like ecoinvent 3.9.1, but without a name. I do not recall it asking for it. But at some point I noticed that the relinking also opened not only one relinking dialogue, but a set of dialogues in parallel, which seemed to have been in a parallel thread. In the end I have this db now – very strange. @Zoophobus, I know this is a terrible description, but could you try importing the attached file against ecoinvent 3.9.1. and see if you get something similar?
Relevant errors
Operating system
Windows 10
Conda environment