Error geting vertex attributes

29 views
Skip to first unread message

jrusse...@gmail.com

unread,
Oct 9, 2020, 10:30:32 AM10/9/20
to brainGraph-help
Hi Chris,

I'm walking through the manual to analyze some rsFMRI data and have run into a problem extracting vertex attributes.  Specifically, when I run this command: 'dt-.V <- rbindlist(lapply(g, vertex_attr_dt)' I get this error message:

Error in `.rowNamesDF<-`(x, value = value) : duplicate 'row.names' are not allowed In addition: Warning message: non-unique values when setting 'row.names': ‘lACCU’, ‘lAMYG’, ‘lcACC’, ‘lCAUD’, ‘lcMFG’, ‘lCUN’, ‘lENT’, ‘lFUS’, ‘lHIPP’, ‘liCC’, ‘lINS’, ‘lIPL’, ‘lITG’, ‘lLING’, ‘lLOF’, ‘lLOG’, ‘lMOF’, ‘lMTG’, ‘lPALL’, ‘lparaC’, ‘lPARH’, ‘lPCC’, ‘lPCUN’, ‘lperiCAL’, ‘lpOPER’, ‘lpORB’, ‘lpostC’, ‘lpreC’, ‘lpTRI’, ‘lPUT’, ‘lrACC’, ‘lrMFG’, ‘lSFG’, ‘lSMAR’, ‘lSPL’, ‘lSTG’, ‘lTHAL’, ‘lTT’, ‘rcACC’, ‘rcMFG’

I'm hoping you might have a suggestion on how to proceed.

Thanks!

jrusse...@gmail.com

unread,
Oct 9, 2020, 10:33:06 AM10/9/20
to brainGraph-help
As a follow up, I'm using v3.0.0 under R v3.6.3

Chris Watson

unread,
Oct 9, 2020, 2:12:34 PM10/9/20
to brainGr...@googlegroups.com
Can you run "traceback()" and post the output?

I need even more details:
1. How do you import your network data?
2. What are the commands you use up to the creation of "g"?
3. If it isn't too large of a file, you can send me the data (I'd need at least "g" and "covars"). It looks like you're using "dkt.scgm" atlas so I don't need that.

Chris

--
You received this message because you are subscribed to the Google Groups "brainGraph-help" group.
To unsubscribe from this group and stop receiving emails from it, send an email to brainGraph-he...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/brainGraph-help/2aa65d11-e149-48a7-82f9-cdad3689ea97n%40googlegroups.com.

jrusse...@gmail.com

unread,
Oct 12, 2020, 9:11:51 AM10/12/20
to brainGraph-help
Hi Chris,
Looks like this was a case of user error.  If this problem gets posted again, it likely stems from chosen atlas not matching what's in the correlation matrices (from DPARSF in my case).  Problem solved. However, I have a second issue I'll post shortly.  Thanks!
Reply all
Reply to author
Forward
0 new messages