jonmcalder/refactor

Issues

• Missing values in input create error in cut.integer

  #25 opened 7 years ago by lorenzwalthert
  0

• right argument without effect in cut.integer for default breaks_mode and breaks as scalars

  #21 opened 8 years ago by lorenzwalthert
  0

• additional warnings at point of factor creation

  #15 opened 8 years ago by lorenzwalthert
  0

• Performance of cut.integer can be improved

  #13 opened 8 years ago by jonmcalder
  1

• cut.ordered argument right without influence

  #18 opened 8 years ago by lorenzwalthert
  0

• uniform call. argument for warnings / errors

  #17 opened 8 years ago by lorenzwalthert
  3

• cut.integer does not produce labels of binwidth when breaks are specified as integer.

  #19 opened 8 years ago by lorenzwalthert
  2

• # making architecture and creation data of factor more accessible

  #16 opened 8 years ago by lorenzwalthert
  0

• breaks given as numeric should be coerced to integer

  #7 opened 8 years ago by lorenzwalthert
  0

• as.cfactor for consistency?

  #12 opened 8 years ago by lorenzwalthert
  0

• `ordered_result` argument in cut.integer and cut.ordered

  #11 opened 8 years ago by lorenzwalthert
  1

• breaks given as integers yield error

  #6 opened 8 years ago by lorenzwalthert
  0

• relationship of the arguments right and balance.

  #2 opened 8 years ago by lorenzwalthert
  1

• bins with width of one

  #8 opened 8 years ago by lorenzwalthert
  1

• include.lowest with inconsistent default

  #1 opened 8 years ago by lorenzwalthert
  2

• extreme input values

  #3 opened 8 years ago by lorenzwalthert
  0