Closed jonathandmoyer closed 3 months ago
PopMigration doesn't work because the names of the fields are not individual years.
PopMigrationYears works fine:
Same PopMigrationYearsWDI:
Hi both,
I'm not familiar with these tables, but somehow I think PopMigration and PopMigrationYears were intentionally made that way. One use the range and other one use the starting year.
What do you suggest we do?
Hmm... When I was looking at this yesterday I wasn't seeing history and forecast for Flex display issues related to migration and I wonder if my use of the dyadic migration model didn't somehow mess that up....
Jonathan D Moyer, PhD Assistant Professor Director Frederick S. Pardee Center for International Futures Josef Korbel School of International Studies University of Denver
On Thu, Feb 22, 2024 at 11:03 AM Yutang @.***> wrote:
Hi both,
I'm not familiar with these tables, but somehow I think PopMigration and PopMigrationYears were intentionally made that way. One use the range and other one use the starting year. image.png (view on web) https://github.com/PardeeCenterDU/IFs-Issues-Tracking/assets/34465524/31d21944-8169-4ab7-88a1-4f327ffc2f8c
What do you suggest we do?
— Reply to this email directly, view it on GitHub https://github.com/PardeeCenterDU/IFs-Issues-Tracking/issues/264#issuecomment-1959986606, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUNOSOX274JJBEJD4ORMGYDYU6CANAVCNFSM6AAAAABDTZOXH6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJZHE4DMNRQGY . You are receiving this because you authored the thread.Message ID: @.***>
Much easier to simply change the column names so that the table can be seen, which, seems to me, is what we did with the PopMigrationYears table.
I've manually fixed this for the next data delivery (IFs8.19)
When I go to Longitudinal Display and try to plot PopMigration (or PopMigrationyears or PopMigrationyearsWDI) I get an error that says there is no data. But there is data in IFsHistSeries. Something is wrong.