Does openNSx really need r+ permissions?

[cpandar]

On line 441 of openNSx.m, it opens the NSx file (via fopen) with 'r+' permissions. This gives it the ability to update the file. One often wants their data to be read-only, to lower the probability of accidentally overwriting the data files. If you do this, though (making your data read-only), because of the r+ permissions used in openNSx, the data fails to load.

So the question is whether the 'r+' permissions are necessary, or if a simple 'r' passed into fopen would do?

Apologies if I'm misunderstanding something.
Best, C

[kianabc]

Hi C, remove the + and see what happens. I don't remember why it was r+. For synching 512 I did some writing back to the file if I remember this correctly. But you'll know for a fact by trying it without the +. Best, Kian

On Mon, Jun 25, 2018 at 9:40 PM Chethan Pandarinath < ***@***.***> wrote: On line 441 of openNSx.m, it opens the NSx file (via fopen) with 'r+' permissions. This gives it the ability to update the file. One often wants their data to be read-only, to lower the probability of accidentally overwriting the data files. If you do this, though (making your data read-only), because of the r+ permissions used in openNSx, the data fails to load. So the question is whether the 'r+' permissions are necessary, or if a simple 'r' passed into fopen would do? Apologies if I'm misunderstanding something. Best, C — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#19>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJSVF_eA2KndawcjT7LfqXzZCTCxV0DKks5uAa0NgaJpZM4U3MVG> .

-- Blackrock Microsystems | blackrockmicro.com Cell: +1-951-254-2686 Schedule a meeting: http://calendly.com/ktorab

[cpandar]

Thanks Kian. I ran it with an 'r' in place of the 'r+', and it worked fine (was able to successfully open an NS3 file and read some LFP data).

I scrolled through the code and I don't see any attempts to write back to the file, so it seems like 'r' should do it.

[kianabc]

Perfect. I don’t remember why it was r+. Age. Does things to you. K

On Tue, Jun 26, 2018 at 7:31 AM Chethan Pandarinath < ***@***.***> wrote: Thanks Kian. I ran it with an 'r' in place of the 'r+', and it worked fine (was able to successfully open an NS3 file and read some LFP data). I scrolled through the code and I don't see any attempts to write back to the file, so it seems like 'r' should do it. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#19 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJSVF4TewD8EuPOf7Z59X-J-L0SiEj3Xks5uAimsgaJpZM4U3MVG> .

-- Blackrock Microsystems | blackrockmicro.com Cell: +1-951-254-2686 Schedule a meeting: http://calendly.com/ktorab

[cpandar]

I definitely understand that...
If it's possible to include this in the next code update, that would be great (would allow us to not have to maintain a separate branch).

[kianabc]

Done.

On Tue, Jun 26, 2018 at 9:25 AM Chethan Pandarinath < ***@***.***> wrote: I definitely understand that... If it's possible to include this in the next code update, that would be great (would allow us to not have to maintain a separate branch). — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#19 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJSVF4KX4gR-smcwTAyPmp65IfEtB9fRks5uAkRSgaJpZM4U3MVG> .

-- Blackrock Microsystems | blackrockmicro.com Cell: +1-951-254-2686 Schedule a meeting: http://calendly.com/ktorab