freenode/#clasp - IRC Chatlog
Search
16:00:31
drmeister
ACTION has trouble figuring out birthdays on a spinning, spherical planet with people in different time zones.
16:01:16
drmeister
It takes a looooong time to find rings in a protein with our current ring finder.
16:08:28
drmeister
Ha ha - I can probably do better here: https://github.com/clasp-developers/clasp/blob/dev/src/core/array.cc#L2154
16:16:32
drmeister
Yes - and what more perfect way is there to celebrate it than with some profile guided optimization!
17:05:41
drmeister
ACTION is looking forward to the Big Cleanup once we get some more resources for programming.
17:08:24
Bike
so what actually uses this? to write it in lisp it would be something like (position 1 bit-vector)
17:10:23
drmeister
I put in array.cc with the hope that it would find a good home in the future in lisp.
17:12:12
drmeister
(position 1 bit-vector) needs to recognize the bit-vector at compile time - that's what you mean?
17:13:04
drmeister
https://github.com/clasp-developers/clasp/blob/dev/src/lisp/kernel/lsp/seqlib.lsp#L440
17:20:59
drmeister
I might have the FEP calculation prototype finished now. I fixed a few little things and sped this up. I restarted the calculation now.
17:46:44
drmeister
Say I have a bit-vector with a fill-pointer and I move the fill-pointer down to a lower value - I'll have to worry about clearing the bits beyond the fill-pointer. Otherwise I'll have to AND the last word of a bit-vector so I don't see garbage bits.
17:49:20
drmeister
Bike: you are good at reading sbcl code - if you get a chance could you check what sbcl does? Do they keep the bit-vector sanitized (zero beyond fill pointer) or do they assume it's garbage and zero it out during tests?
18:34:11
beach
I don't think what's beyond the fill pointer is "garbage". There are functions that ignore the fill pointer, like AREF and BIT. They should still work as advertised I assume.
18:35:02
beach
(defparameter *b* (make-array 234 :element-type 'bit :initial-element 0 :fill-pointer 33))
18:35:20
drmeister
I thought I when working with entire bit-vectors that I had two options (1) clear the bits at the end of the vector for every operation on all the bits (2) keep the bits at the end of the vector clear all the time.
18:36:16
beach
My immediate reaction is that you don't have the right to alter the bits beyond the fill pointer when you adjust it.