fabiogiglietto/CooRnet

Error from `get_top_coord_shares` : Column `title` doesn't exist.

billy3321 opened this issue · 2 comments

I use get_top_coord_shares like tutorial here:

https://dfrlab.github.io/Plandemic/

And I got error: Column title doesn't exist.

> top_shares_per_components <- get_top_coord_shares(output, order_by = "engagement", component = TRUE, top = 10)
Error in `dplyr::select()`:
! Can't subset columns that don't exist.
✖ Column `title` doesn't exist.
Run `rlang::last_error()` to see where the error occurred.
> rlang::last_error()
<error/vctrs_error_subscript_oob>
Error in `dplyr::select()`:
! Can't subset columns that don't exist.
✖ Column `title` doesn't exist.
---
Backtrace:
  1. CooRnet::get_top_coord_shares(...)
  5. dplyr:::select.data.frame(...)
  8. tidyselect::eval_select(expr(c(...)), .data)
  9. tidyselect:::eval_select_impl(...)
 18. tidyselect:::vars_select_eval(...)
 19. tidyselect:::walk_data_tree(expr, data_mask, context_mask, error_call)
 20. tidyselect:::eval_c(expr, data_mask, context_mask)
 21. tidyselect:::reduce_sels(node, data_mask, context_mask, init = init)
 22. tidyselect:::walk_data_tree(new, data_mask, context_mask)
 23. tidyselect:::eval_c(expr, data_mask, context_mask)
 24. tidyselect:::reduce_sels(node, data_mask, context_mask, init = init)
 25. tidyselect:::walk_data_tree(new, data_mask, context_mask)
 26. tidyselect:::as_indices_sel_impl(...)
 27. tidyselect:::as_indices_impl(x, vars, call = call, strict = strict)
 28. tidyselect:::chr_as_locations(x, vars, call = call)
 29. vctrs::vec_as_location(x, n = length(vars), names = vars)
 30. vctrs `<fn>`()
 31. vctrs:::stop_subscript_oob(...)
 32. vctrs:::stop_subscript(...)
Run `rlang::last_trace()` to see the full context.
> rlang::last_trace()
<error/vctrs_error_subscript_oob>
Error in `dplyr::select()`:
! Can't subset columns that don't exist.
✖ Column `title` doesn't exist.
---
Backtrace:
     ▆
  1. ├─CooRnet::get_top_coord_shares(...)
  2. │ └─... %>% as.data.frame()
  3. ├─base::as.data.frame(.)
  4. ├─dplyr::select(...)
  5. └─dplyr:::select.data.frame(...)
  6.   ├─dplyr:::tidyselect_fix_call(...)
  7.   │ └─base::withCallingHandlers(...)
  8.   └─tidyselect::eval_select(expr(c(...)), .data)
  9.     └─tidyselect:::eval_select_impl(...)
 10.       ├─tidyselect:::with_subscript_errors(...)
 11.       │ ├─base::tryCatch(...)
 12.       │ │ └─base tryCatchList(expr, classes, parentenv, handlers)
 13.       │ │   └─base tryCatchOne(expr, names, parentenv, handlers[[1L]])
 14.       │ │     └─base doTryCatch(return(expr), name, parentenv, handler)
 15.       │ └─tidyselect:::with_entraced_errors(expr)
 16.       │   └─rlang::try_fetch(...)
 17.       │     └─base::withCallingHandlers(...)
 18.       └─tidyselect:::vars_select_eval(...)
 19.         └─tidyselect:::walk_data_tree(expr, data_mask, context_mask, error_call)
 20.           └─tidyselect:::eval_c(expr, data_mask, context_mask)
 21.             └─tidyselect:::reduce_sels(node, data_mask, context_mask, init = init)
 22.               └─tidyselect:::walk_data_tree(new, data_mask, context_mask)
 23.                 └─tidyselect:::eval_c(expr, data_mask, context_mask)
 24.                   └─tidyselect:::reduce_sels(node, data_mask, context_mask, init = init)
 25.                     └─tidyselect:::walk_data_tree(new, data_mask, context_mask)
 26.                       └─tidyselect:::as_indices_sel_impl(...)
 27.                         └─tidyselect:::as_indices_impl(x, vars, call = call, strict = strict)
 28.                           └─tidyselect:::chr_as_locations(x, vars, call = call)
 29.                             └─vctrs::vec_as_location(x, n = length(vars), names = vars)
 30.                               └─vctrs `<fn>`()
 31.                                 └─vctrs:::stop_subscript_oob(...)
 32.                                   └─vctrs:::stop_subscript(...)
 33.                                     └─rlang::abort(...)

I think maybe the API of facebook did change, and need to fix it.

Hi :)
in the other issue you mentioned that get_coord_shares raised an error. However, you are now using here an output created by get_coord_shares. Are you still having issues with get_coord_shares?

still

Yes :( I did use the output generate by get_coord_shares and it shows error...