PardeeCenterDU / IFs-Issues-Tracking

This repository only holds the list of bugs that have been reported for IFs. Anyone may add a bug report, but please look to see if your issue has already been added!
2 stars 0 forks source link

Make a table exogenous through IFs #288

Open quciet opened 3 months ago

quciet commented 3 months ago

Hi all,

I'm hoping to add a feature in IFs to make a table exogenous through IFs interface. So far the process looks like this,

  1. Import desired tables into IFs.
  2. Add new rows into IFsExogenousVars under the IFs.db file with each table assigning their associated model IDs. Normally, this model id (ExogenousModelId column) should not be duplicated with existing ones.
  3. Create a scenario in IFs and make sure the scenario is calling the right model id to make those tables exogenous.

Both step 1 & 3 can be done entirely through IFs interface (Extended Features and Scenario Analysis respectively). Maybe we can add a feature for step 2 to avoid having users to deal with SQLite databases? Maybe in Extended Features or Scenario Analysis, we can add a feature saying "Make an Exogenous Table" and people can search and click a table from IFsHistSeries.db. Then there will be a guided process to tell users to add model id and other information.

This is a nice-to-have feature from my perspective. But I can lower the prioty if you don't think this would be much helpful.

jonathandmoyer commented 3 months ago

Hi Yutang:

We need to turn in the Star Protocol piece soon, so a new feature won't be possible. I'm not sure why it's a very large ask to get people to update a data table in SQL Lite--can you explain your concerns?

Jonathan D Moyer, PhD Assistant Professor Director Frederick S. Pardee Center for International Futures Josef Korbel School of International Studies University of Denver

On Tue, Apr 2, 2024 at 2:37 PM Yutang @.***> wrote:

Hi all,

I'm hoping if it is possible to add a feature in IFs to make a table exogenous through IFs interface. So far the process looks like this,

  1. Import desired tables into IFs.
  2. Add new rows into IFsExogenousVars under the IFs.db file with each table assigning their associated model IDs. Normally, this model id (ExogenousModelId column) should not be duplicated with existing ones.
  3. Create a scenario in IFs and make sure the scenario is calling the right model id to make those tables exogenous.

Both step 1 & 3 can be done entirely through IFs interface (Extended Features and Scenario Analysis respectively). Maybe we can add a feature for step 2 to avoid having users to deal with SQLite databases? Maybe in Extended Features or Scenario Analysis, we can add a feature saying "Make an Exogenous Table" and people can search and click a table from IFsHistSeries.db. Then there will be a guided process to tell users to add model id and other information.

This is a nice-to-have feature from my perspective. But I can lower the prioty if you don't think this would be much helpful.

— Reply to this email directly, view it on GitHub https://github.com/PardeeCenterDU/IFs-Issues-Tracking/issues/288, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUNOSOQN5KPZZ34MK2A2ER3Y3MJJNAVCNFSM6AAAAABFUCES7KVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZDCNBQGE4TKOI . You are receiving this because you were assigned.Message ID: @.***>

quciet commented 3 months ago

Hi Yutang: We need to turn in the Star Protocol piece soon, so a new feature won't be possible. I'm not sure why it's a very large ask to get people to update a data table in SQL Lite--can you explain your concerns? ----- Jonathan D Moyer, PhD Assistant Professor Director Frederick S. Pardee Center for International Futures Josef Korbel School of International Studies University of Denver On Tue, Apr 2, 2024 at 2:37 PM Yutang @.> wrote: Hi all, I'm hoping if it is possible to add a feature in IFs to make a table exogenous through IFs interface. So far the process looks like this, 1. Import desired tables into IFs. 2. Add new rows into IFsExogenousVars under the IFs.db file with each table assigning their associated model IDs. Normally, this model id (ExogenousModelId column) should not be duplicated with existing ones. 3. Create a scenario in IFs and make sure the scenario is calling the right model id to make those tables exogenous. Both step 1 & 3 can be done entirely through IFs interface (Extended Features and Scenario Analysis respectively). Maybe we can add a feature for step 2 to avoid having users to deal with SQLite databases? Maybe in Extended Features or Scenario Analysis, we can add a feature saying "Make an Exogenous Table" and people can search and click a table from IFsHistSeries.db. Then there will be a guided process to tell users to add model id and other information. This is a nice-to-have feature from my perspective. But I can lower the prioty if you don't think this would be much helpful. — Reply to this email directly, view it on GitHub <#288>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUNOSOQN5KPZZ34MK2A2ER3Y3MJJNAVCNFSM6AAAAABFUCES7KVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZDCNBQGE4TKOI . You are receiving this because you were assigned.Message ID: @.>

Thanks for the quick reply, Jon.

Indeed I was considering this feature because of the the Star Protocol piece. But I'm not asking for this feature to be added for the Star Protocol piece. We will still provide the instructions on how to update a data table in SQLite. That's why I think this is a preferable feature but not a neccesarry one. Hence, a priority 3 or even lower if you want.

jonathandmoyer commented 1 month ago

I'm going to lower the priority on this because the STAR Protocol piece will allow users to make series exogenous...