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
Emerging from the discussion of #1120, we have resolved that the gene table should itself have a timestamp. Even if a high percentage of genes will be the same from year to year, producing nearly the same records, we also don’t want to include genes that didn’t exist at a particular time with the interactions from that time
The text was updated successfully, but these errors were encountered:
@ceciliazaragoza reported that initial queries that include the timestamp now run without errors, but for ZAP1, which regulates itself, the updated query does not return the expected self-regulation adjacency item
@kdahlquist checked the 2025 data and confirmed that ZAP1 does still regulate itself, so @ceciliazaragoza will investigate the query further. @ntran18 can investigate the latest loaded data to see if the issue resides in the database scripts instead
The issue with ZAP1 is not from the database queries but from the scripts that getting data from AllianceMine. I checked the script, and we don't get data that have ZAP1 self-regulated. I have to investigate the queries more.
Emerging from the discussion of #1120, we have resolved that the gene table should itself have a timestamp. Even if a high percentage of genes will be the same from year to year, producing nearly the same records, we also don’t want to include genes that didn’t exist at a particular time with the interactions from that time
The text was updated successfully, but these errors were encountered: