`NIL' is not of the expected type `NUMBER' error

[davipatti]

Attempting to merge an HI table into a save using the gui command Merge table into save (and optimize, freezing points in original save)

Save: https://gist.github.com/davipatti/9dfd710d3ec634bd422ddb21be51123c Hi table: https://gist.github.com/davipatti/441b1978d58a8992fb33d562b9d1d6c6

I can open and optimize both the save and HI table alone. But merging generates the following error:

CL-USER(1):

Warning: Not carrying forward any row or col adjusts.
9246776 bytes have been tenured, next gc will be global.
See the documentation for variable *GLOBAL-GC-BEHAVIOR* for more information.
9089504 bytes have been tenured, next gc will be global.
See the documentation for variable *GLOBAL-GC-BEHAVIOR* for more information.
Error: `NIL' is not of the expected type `NUMBER'
  [condition type: TYPE-ERROR]

Restart actions (select using :continue):
 0: Abort entirely from this (lisp) process.
[Current process: background-tk-listener]

[Nicolaaht]

Hi David

table into save merging (frozen) hasn’t worked for years (circa 2009) - at least on the macs I have had. I know Bjorn found similar. I also don’t remember the relaxed table into save function working either since about then (i.e. without map point frozen), after which I used the chain function on acmacs to merge and then output the merged save in lispmds format.

Nic

On 14 Sep 2017, at 15:38, David Pattinson notifications@github.com wrote:

Attempting to merge an HI table into a save using the gui command Merge table into save (and optimize, freezing points in original save)

Save: https://gist.github.com/davipatti/9dfd710d3ec634bd422ddb21be51123c https://gist.github.com/davipatti/9dfd710d3ec634bd422ddb21be51123c Hi table: https://gist.github.com/davipatti/441b1978d58a8992fb33d562b9d1d6c6 https://gist.github.com/davipatti/441b1978d58a8992fb33d562b9d1d6c6 I can open and optimize both the save and HI table alone. But merging generates the following error:

CL-USER(1):

Warning: Not carrying forward any row or col adjusts. 9246776 bytes have been tenured, next gc will be global. See the documentation for variable GLOBAL-GC-BEHAVIOR for more information. 9089504 bytes have been tenured, next gc will be global. See the documentation for variable GLOBAL-GC-BEHAVIOR for more information. Error: NIL' is not of the expected typeNUMBER' [condition type: TYPE-ERROR]

Restart actions (select using :continue): 0: Abort entirely from this (lisp) process. [Current process: background-tk-listener] — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/acorg/lispmds/issues/26, or mute the thread https://github.com/notifications/unsubscribe-auth/AL1ouMZzQ9g2HTny0di_PFFL_9ODlLHmks5siTp5gaJpZM4PXsHE.

[davipatti]

I've been using this exact option a lot for the last few weeks and it's worked fine. Here are some example data on which it works fine:

save: https://gist.github.com/davipatti/9db4e1d3979ac27b4965e1969d1f0c20 hi: https://gist.github.com/davipatti/405d198ffabc3e24573cf317b2c517ca

[Nicolaaht]

And you have done the usual cross-checks on number of sera/antigens in common and nomenclature?

N

On 14 Sep 2017, at 15:57, David Pattinson notifications@github.com wrote:

I've been using this exact option a lot for the last few weeks and it's worked fine. Here are some example data on which it works fine:

save: https://gist.github.com/davipatti/9db4e1d3979ac27b4965e1969d1f0c20 https://gist.github.com/davipatti/9db4e1d3979ac27b4965e1969d1f0c20 hi: https://gist.github.com/davipatti/405d198ffabc3e24573cf317b2c517ca https://gist.github.com/davipatti/405d198ffabc3e24573cf317b2c517ca — You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/acorg/lispmds/issues/26#issuecomment-329509041, or mute the thread https://github.com/notifications/unsubscribe-auth/AL1ouG6jLbPoA7pkPrwdTzNQ1pXjXvyIks5siT7igaJpZM4PXsHE.

[davipatti]

There are 17 common sera, 0 common antigens.

[davipatti]

Opening the save in the GUI, re-saving it, and then running the merge with that re-saved version works fine. Here is the re-saved version of the original save that can be merged into: https://gist.github.com/davipatti/c1a8672708fcf0dd063b20d38ea0bfb2

[Nicolaaht]

The dark art of lispmds cartography!

I’ll leave others more expert to comment :) I’ve only had the above error occur with insufficient commonality but have not tried your fix below.

N

On 14 Sep 2017, at 16:08, David Pattinson notifications@github.com wrote:

Opening the save in the GUI, re-saving it, and then running the merge with that re-saved version works fine. Here is the re-saved version of the original save https://gist.github.com/davipatti/9dfd710d3ec634bd422ddb21be51123c that can be merged into: https://gist.github.com/davipatti/c1a8672708fcf0dd063b20d38ea0bfb2 https://gist.github.com/davipatti/c1a8672708fcf0dd063b20d38ea0bfb2 — You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/acorg/lispmds/issues/26#issuecomment-329512457, or mute the thread https://github.com/notifications/unsubscribe-auth/AL1ouPk9VfcKt6LXkxI_PbEoWCkYoxRDks5siUFhgaJpZM4PXsHE.

[davidfburke]

I think that DIM-ANNEAL-ENDING-DIMENSION argument to add-table-to-save-and-run-randomizing-only-new-points is set to NIL by default. If there are no :MDS-DIMENSIONS '2 set in the save, then this causes errors. Try typing the following into the lisp prompt before merging :trace add-table-to-save-and-run-randomizing-only-new-points