The graph file does not seem to be here

[BigVulcanDeal]

I was unable to find the graph file. I did generate a new AlexNet graph file, but it was on my NCS dev machine, which has the NCSDK2 branch. I get the following when I try to run stuff: ready NCS device found: 3 NCS device Opened. NCS Device opened normally. Graph file loaded. Could not allocate graph for file: graph Error from mvncAllocateGraph is: -10

Thinking that maybe the graph file has firmware dependent I tried the mvcmd file that ships with the NCS2 SDK (it's a little larger, so something about it is different). In any case, basically the same results in the OUTPUT and DEBUG windows.

[donnaware]

The graph file is too big for GitHub, it is like 100MB so GitHub wont accept it. Even zipped.

So you have to create it I guess, best way is to do it on an Ubuntu VM, I think it is possible to do on windows but you have to load a lot of stuff to get that to work and it seemed very fiddly. It would be nice if there was an easy way to make the graph file in windows.

Anyhow, I created the graph file using the standard Ubuntu environment and then just copied it over to windows and that works.

Maybe someday someone will find a way to make an exe program to make the graph file or some other simpler way.

From: BigVulcanDeal Sent: Friday, November 23, 2018 2:42 PM To: donnaware/movidius_windows Cc: Subscribed Subject: [donnaware/movidius_windows] The graph file does not seem to be here(#4)

I was unable to find the graph file. I did generate a new AlexNet graph file, but it was on my NCS dev machine, which has the NCSDK2 branch. I get the following when I try to run stuff: ready NCS device found: 3 NCS device Opened. NCS Device opened normally. Graph file loaded. Could not allocate graph for file: graph Error from mvncAllocateGraph is: -10 Thinking that maybe the graph file has firmware dependent I tried the mvcmd file that ships with the NCS2 SDK (it's a little larger, so something about it is different). In any case, basically the same results in the OUTPUT and DEBUG windows. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[BigVulcanDeal]

I did do that, by building the AlexNet example under ncsdk/examples/caffe/AlexNet/ .. but for the NCSDK2 branch. Your mvcd file is a tad smaller than the one with the NCSDK 2, so I presume you that you based your example on the older branch (which is on GitHub as the "master" branch of the ncsdk),

In any case, I certainly don't expect you to take the time to test it to see if it works with your stuff, but .. just in case you are bored, here's a link to a Google Drive folder with the graph file in it. I built it on a Ubuntu VM, from the NCSDK 2. https://drive.google.com/drive/folders/1-CgduNbh9-WhrOEpz8hkaIkaeuP_jzeL

Or I can maybe build the whole app, including a static version of the DLL so that it's easy to debug, but it's kind of a pain in the neck .. I guess I could install CodeBlocks or something like that. But what I'm really trying to do get a Pi to work with the NCS 2 .. and Intel hasn't released the NCS releant source code for OpenVINO .. so it's frustratingly difficult to figure out how to make this "Edge Device" actually work on edge hardware.

Thanks again for making that example .. very instructive!

On Sat, Nov 24, 2018 at 1:16 AM Donna notifications@github.com wrote:

The graph file is too big for GitHub, it is like 100MB so GitHub wont accept it. Even zipped.

So you have to create it I guess, best way is to do it on an Ubuntu VM, I think it is possible to do on windows but you have to load a lot of stuff to get that to work and it seemed very fiddly. It would be nice if there was an easy way to make the graph file in windows.

Anyhow, I created the graph file using the standard Ubuntu environment and then just copied it over to windows and that works.

Maybe someday someone will find a way to make an exe program to make the graph file or some other simpler way.

From: BigVulcanDeal Sent: Friday, November 23, 2018 2:42 PM To: donnaware/movidius_windows Cc: Subscribed Subject: [donnaware/movidius_windows] The graph file does not seem to be here(#4)

I was unable to find the graph file. I did generate a new AlexNet graph file, but it was on my NCS dev machine, which has the NCSDK2 branch. I get the following when I try to run stuff: ready NCS device found: 3 NCS device Opened. NCS Device opened normally. Graph file loaded. Could not allocate graph for file: graph Error from mvncAllocateGraph is: -10 Thinking that maybe the graph file has firmware dependent I tried the mvcmd file that ships with the NCS2 SDK (it's a little larger, so something about it is different). In any case, basically the same results in the OUTPUT and DEBUG windows. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441346702, or mute the thread https://github.com/notifications/unsubscribe-auth/AA_UzuyQckWXJ-IAUBgLvVc8WZWP3ouSks5uyORIgaJpZM4YxKzF .

[donnaware]

Oh, well I could drop my graph file into that google drive if you want.

It could be I was using an older version, I was messing with this a while back but am on another project right now.

When you say you are trying to get a Pi to with NCS2, do you mean a Raspberry Pi board ? Because I was Thinking about that too, that would be fun.

Intel stuff is not always supported all that well I have noticed. The Myriad chips are really cool but it is difficult to get it to work on different platforms. My project was to get it to work on a Lattepanda board which I accomplished. It seems like it might be easier to get it to work on a Linux board tho, like the RPI

Sorry I cannot be of more help.

From: BigVulcanDeal Sent: Friday, November 23, 2018 10:49 PM To: donnaware/movidius_windows Cc: Donna; Comment Subject: Re: [donnaware/movidius_windows] The graph file does not seem to behere (#4)

I did do that, by building the AlexNet example under ncsdk/examples/caffe/AlexNet/ .. but for the NCSDK2 branch. Your mvcd file is a tad smaller than the one with the NCSDK 2, so I presume you that you based your example on the older branch (which is on GitHub as the "master" branch of the ncsdk),

In any case, I certainly don't expect you to take the time to test it to see if it works with your stuff, but .. just in case you are bored, here's a link to a Google Drive folder with the graph file in it. I built it on a Ubuntu VM, from the NCSDK 2. https://drive.google.com/drive/folders/1-CgduNbh9-WhrOEpz8hkaIkaeuP_jzeL

Or I can maybe build the whole app, including a static version of the DLL so that it's easy to debug, but it's kind of a pain in the neck .. I guess I could install CodeBlocks or something like that. But what I'm really trying to do get a Pi to work with the NCS 2 .. and Intel hasn't released the NCS releant source code for OpenVINO .. so it's frustratingly difficult to figure out how to make this "Edge Device" actually work on edge hardware.

Thanks again for making that example .. very instructive!

On Sat, Nov 24, 2018 at 1:16 AM Donna notifications@github.com wrote:

The graph file is too big for GitHub, it is like 100MB so GitHub wont accept it. Even zipped.

So you have to create it I guess, best way is to do it on an Ubuntu VM, I think it is possible to do on windows but you have to load a lot of stuff to get that to work and it seemed very fiddly. It would be nice if there was an easy way to make the graph file in windows.

Anyhow, I created the graph file using the standard Ubuntu environment and then just copied it over to windows and that works.

Maybe someday someone will find a way to make an exe program to make the graph file or some other simpler way.

From: BigVulcanDeal Sent: Friday, November 23, 2018 2:42 PM To: donnaware/movidius_windows Cc: Subscribed Subject: [donnaware/movidius_windows] The graph file does not seem to be here(#4)

I was unable to find the graph file. I did generate a new AlexNet graph file, but it was on my NCS dev machine, which has the NCSDK2 branch. I get the following when I try to run stuff: ready NCS device found: 3 NCS device Opened. NCS Device opened normally. Graph file loaded. Could not allocate graph for file: graph Error from mvncAllocateGraph is: -10 Thinking that maybe the graph file has firmware dependent I tried the mvcmd file that ships with the NCS2 SDK (it's a little larger, so something about it is different). In any case, basically the same results in the OUTPUT and DEBUG windows. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441346702, or mute the thread https://github.com/notifications/unsubscribe-auth/AA_UzuyQckWXJ-IAUBgLvVc8WZWP3ouSks5uyORIgaJpZM4YxKzF .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[BigVulcanDeal]

I changed the folder to allow anyone with the link to write. If your graph doesn't work on my system, then I know it's something other than 'old NCSDK vs new NCSDK"

I think the original NCS modules work fine with the RPi, and they should work even better with the new Pi 3 B+, since it has USB 3.0 ..

The OpenVINO stuff is clever, in theory, but it's really complex compared to the old ncsdk. It basically takes an intermediate graph representation and then can compile it for a number of targets. With access to the source code, it would not be hard to break that into two parts .. one part runs on the dev system and produces an NCS binary graph that can be uploaded and the other part is a bit like your sample app .. it sets up the NCS, uploads the binary graph, and then shovels images in and grabs results.

On Sat, Nov 24, 2018, 2:02 AM Donna <notifications@github.com wrote:

Oh, well I could drop my graph file into that google drive if you want.

It could be I was using an older version, I was messing with this a while back but am on another project right now.

When you say you are trying to get a Pi to with NCS2, do you mean a Raspberry Pi board ? Because I was Thinking about that too, that would be fun.

Intel stuff is not always supported all that well I have noticed. The Myriad chips are really cool but it is difficult to get it to work on different platforms. My project was to get it to work on a Lattepanda board which I accomplished. It seems like it might be easier to get it to work on a Linux board tho, like the RPI

Sorry I cannot be of more help.

From: BigVulcanDeal Sent: Friday, November 23, 2018 10:49 PM To: donnaware/movidius_windows Cc: Donna; Comment Subject: Re: [donnaware/movidius_windows] The graph file does not seem to behere (#4)

I did do that, by building the AlexNet example under ncsdk/examples/caffe/AlexNet/ .. but for the NCSDK2 branch. Your mvcd file is a tad smaller than the one with the NCSDK 2, so I presume you that you based your example on the older branch (which is on GitHub as the "master" branch of the ncsdk),

In any case, I certainly don't expect you to take the time to test it to see if it works with your stuff, but .. just in case you are bored, here's a link to a Google Drive folder with the graph file in it. I built it on a Ubuntu VM, from the NCSDK 2. https://drive.google.com/drive/folders/1-CgduNbh9-WhrOEpz8hkaIkaeuP_jzeL

Or I can maybe build the whole app, including a static version of the DLL so that it's easy to debug, but it's kind of a pain in the neck .. I guess I could install CodeBlocks or something like that. But what I'm really trying to do get a Pi to work with the NCS 2 .. and Intel hasn't released the NCS releant source code for OpenVINO .. so it's frustratingly difficult to figure out how to make this "Edge Device" actually work on edge hardware.

Thanks again for making that example .. very instructive!

On Sat, Nov 24, 2018 at 1:16 AM Donna notifications@github.com wrote:

The graph file is too big for GitHub, it is like 100MB so GitHub wont accept it. Even zipped.

So you have to create it I guess, best way is to do it on an Ubuntu VM, I think it is possible to do on windows but you have to load a lot of stuff to get that to work and it seemed very fiddly. It would be nice if there was an easy way to make the graph file in windows.

Anyhow, I created the graph file using the standard Ubuntu environment and then just copied it over to windows and that works.

Maybe someday someone will find a way to make an exe program to make the graph file or some other simpler way.

From: BigVulcanDeal Sent: Friday, November 23, 2018 2:42 PM To: donnaware/movidius_windows Cc: Subscribed Subject: [donnaware/movidius_windows] The graph file does not seem to be here(#4)

I was unable to find the graph file. I did generate a new AlexNet graph file, but it was on my NCS dev machine, which has the NCSDK2 branch. I get the following when I try to run stuff: ready NCS device found: 3 NCS device Opened. NCS Device opened normally. Graph file loaded. Could not allocate graph for file: graph Error from mvncAllocateGraph is: -10 Thinking that maybe the graph file has firmware dependent I tried the mvcmd file that ships with the NCS2 SDK (it's a little larger, so something about it is different). In any case, basically the same results in the OUTPUT and DEBUG windows. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441346702 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AA_UzuyQckWXJ-IAUBgLvVc8WZWP3ouSks5uyORIgaJpZM4YxKzF

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441348481, or mute the thread https://github.com/notifications/unsubscribe-auth/AA_Uzs3r57pUp_0QITWxiKTUFX6seektks5uyO7ugaJpZM4YxKzF .

[donnaware]

OK, it’s uploading, it says 3hrs left, LOL. Crazy

That openvino looks interesting, they sure make it look easy in their quick start guide !

From: BigVulcanDeal Sent: Friday, November 23, 2018 11:33 PM To: donnaware/movidius_windows Cc: Donna; Comment Subject: Re: [donnaware/movidius_windows] The graph file does not seem to behere (#4)

I changed the folder to allow anyone with the link to write. If your graph doesn't work on my system, then I know it's something other than 'old NCSDK vs new NCSDK"

I think the original NCS modules work fine with the RPi, and they should work even better with the new Pi 3 B+, since it has USB 3.0 ..

The OpenVINO stuff is clever, in theory, but it's really complex compared to the old ncsdk. It basically takes an intermediate graph representation and then can compile it for a number of targets. With access to the source code, it would not be hard to break that into two parts .. one part runs on the dev system and produces an NCS binary graph that can be uploaded and the other part is a bit like your sample app .. it sets up the NCS, uploads the binary graph, and then shovels images in and grabs results.

On Sat, Nov 24, 2018, 2:02 AM Donna <notifications@github.com wrote:

Oh, well I could drop my graph file into that google drive if you want.

It could be I was using an older version, I was messing with this a while back but am on another project right now.

When you say you are trying to get a Pi to with NCS2, do you mean a Raspberry Pi board ? Because I was Thinking about that too, that would be fun.

Intel stuff is not always supported all that well I have noticed. The Myriad chips are really cool but it is difficult to get it to work on different platforms. My project was to get it to work on a Lattepanda board which I accomplished. It seems like it might be easier to get it to work on a Linux board tho, like the RPI

Sorry I cannot be of more help.

From: BigVulcanDeal Sent: Friday, November 23, 2018 10:49 PM To: donnaware/movidius_windows Cc: Donna; Comment Subject: Re: [donnaware/movidius_windows] The graph file does not seem to behere (#4)

I did do that, by building the AlexNet example under ncsdk/examples/caffe/AlexNet/ .. but for the NCSDK2 branch. Your mvcd file is a tad smaller than the one with the NCSDK 2, so I presume you that you based your example on the older branch (which is on GitHub as the "master" branch of the ncsdk),

In any case, I certainly don't expect you to take the time to test it to see if it works with your stuff, but .. just in case you are bored, here's a link to a Google Drive folder with the graph file in it. I built it on a Ubuntu VM, from the NCSDK 2. https://drive.google.com/drive/folders/1-CgduNbh9-WhrOEpz8hkaIkaeuP_jzeL

Or I can maybe build the whole app, including a static version of the DLL so that it's easy to debug, but it's kind of a pain in the neck .. I guess I could install CodeBlocks or something like that. But what I'm really trying to do get a Pi to work with the NCS 2 .. and Intel hasn't released the NCS releant source code for OpenVINO .. so it's frustratingly difficult to figure out how to make this "Edge Device" actually work on edge hardware.

Thanks again for making that example .. very instructive!

On Sat, Nov 24, 2018 at 1:16 AM Donna notifications@github.com wrote:

The graph file is too big for GitHub, it is like 100MB so GitHub wont accept it. Even zipped.

So you have to create it I guess, best way is to do it on an Ubuntu VM, I think it is possible to do on windows but you have to load a lot of stuff to get that to work and it seemed very fiddly. It would be nice if there was an easy way to make the graph file in windows.

Anyhow, I created the graph file using the standard Ubuntu environment and then just copied it over to windows and that works.

Maybe someday someone will find a way to make an exe program to make the graph file or some other simpler way.

From: BigVulcanDeal Sent: Friday, November 23, 2018 2:42 PM To: donnaware/movidius_windows Cc: Subscribed Subject: [donnaware/movidius_windows] The graph file does not seem to be here(#4)

I was unable to find the graph file. I did generate a new AlexNet graph file, but it was on my NCS dev machine, which has the NCSDK2 branch. I get the following when I try to run stuff: ready NCS device found: 3 NCS device Opened. NCS Device opened normally. Graph file loaded. Could not allocate graph for file: graph Error from mvncAllocateGraph is: -10 Thinking that maybe the graph file has firmware dependent I tried the mvcmd file that ships with the NCS2 SDK (it's a little larger, so something about it is different). In any case, basically the same results in the OUTPUT and DEBUG windows. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441346702 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AA_UzuyQckWXJ-IAUBgLvVc8WZWP3ouSks5uyORIgaJpZM4YxKzF

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441348481, or mute the thread https://github.com/notifications/unsubscribe-auth/AA_Uzs3r57pUp_0QITWxiKTUFX6seektks5uyO7ugaJpZM4YxKzF .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[BigVulcanDeal]

Thanks for the upload!

OpenVINO is easy .. on an Intel platform. It's just not so easy to host on a y device that is cheap enough to be considered an and it's not very "open", really.

On Sat, Nov 24, 2018, 2:57 AM Donna <notifications@github.com wrote:

OK, it’s uploading, it says 3hrs left, LOL. Crazy

That openvino looks interesting, they sure make it look easy in their quick start guide !

From: BigVulcanDeal Sent: Friday, November 23, 2018 11:33 PM To: donnaware/movidius_windows Cc: Donna; Comment Subject: Re: [donnaware/movidius_windows] The graph file does not seem to behere (#4)

I changed the folder to allow anyone with the link to write. If your graph doesn't work on my system, then I know it's something other than 'old NCSDK vs new NCSDK"

I think the original NCS modules work fine with the RPi, and they should work even better with the new Pi 3 B+, since it has USB 3.0 ..

The OpenVINO stuff is clever, in theory, but it's really complex compared to the old ncsdk. It basically takes an intermediate graph representation and then can compile it for a number of targets. With access to the source code, it would not be hard to break that into two parts .. one part runs on the dev system and produces an NCS binary graph that can be uploaded and the other part is a bit like your sample app .. it sets up the NCS, uploads the binary graph, and then shovels images in and grabs results.

On Sat, Nov 24, 2018, 2:02 AM Donna <notifications@github.com wrote:

Oh, well I could drop my graph file into that google drive if you want.

It could be I was using an older version, I was messing with this a while back but am on another project right now.

When you say you are trying to get a Pi to with NCS2, do you mean a Raspberry Pi board ? Because I was Thinking about that too, that would be fun.

Intel stuff is not always supported all that well I have noticed. The Myriad chips are really cool but it is difficult to get it to work on different platforms. My project was to get it to work on a Lattepanda board which I accomplished. It seems like it might be easier to get it to work on a Linux board tho, like the RPI

Sorry I cannot be of more help.

From: BigVulcanDeal Sent: Friday, November 23, 2018 10:49 PM To: donnaware/movidius_windows Cc: Donna; Comment Subject: Re: [donnaware/movidius_windows] The graph file does not seem to behere (#4)

I did do that, by building the AlexNet example under ncsdk/examples/caffe/AlexNet/ .. but for the NCSDK2 branch. Your mvcd file is a tad smaller than the one with the NCSDK 2, so I presume you that you based your example on the older branch (which is on GitHub as the "master" branch of the ncsdk),

In any case, I certainly don't expect you to take the time to test it to see if it works with your stuff, but .. just in case you are bored, here's a link to a Google Drive folder with the graph file in it. I built it on a Ubuntu VM, from the NCSDK 2. https://drive.google.com/drive/folders/1-CgduNbh9-WhrOEpz8hkaIkaeuP_jzeL

Or I can maybe build the whole app, including a static version of the DLL so that it's easy to debug, but it's kind of a pain in the neck .. I guess I could install CodeBlocks or something like that. But what I'm really trying to do get a Pi to work with the NCS 2 .. and Intel hasn't released the NCS releant source code for OpenVINO .. so it's frustratingly difficult to figure out how to make this "Edge Device" actually work on edge hardware.

Thanks again for making that example .. very instructive!

On Sat, Nov 24, 2018 at 1:16 AM Donna notifications@github.com wrote:

The graph file is too big for GitHub, it is like 100MB so GitHub wont accept it. Even zipped.

So you have to create it I guess, best way is to do it on an Ubuntu VM, I think it is possible to do on windows but you have to load a lot of stuff to get that to work and it seemed very fiddly. It would be nice if there was an easy way to make the graph file in windows.

Anyhow, I created the graph file using the standard Ubuntu environment and then just copied it over to windows and that works.

Maybe someday someone will find a way to make an exe program to make the graph file or some other simpler way.

From: BigVulcanDeal Sent: Friday, November 23, 2018 2:42 PM To: donnaware/movidius_windows Cc: Subscribed Subject: [donnaware/movidius_windows] The graph file does not seem to be here(#4)

I was unable to find the graph file. I did generate a new AlexNet graph file, but it was on my NCS dev machine, which has the NCSDK2 branch. I get the following when I try to run stuff: ready NCS device found: 3 NCS device Opened. NCS Device opened normally. Graph file loaded. Could not allocate graph for file: graph Error from mvncAllocateGraph is: -10 Thinking that maybe the graph file has firmware dependent I tried the mvcmd file that ships with the NCS2 SDK (it's a little larger, so something about it is different). In any case, basically the same results in the OUTPUT and DEBUG windows. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441346702

, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AA_UzuyQckWXJ-IAUBgLvVc8WZWP3ouSks5uyORIgaJpZM4YxKzF

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441348481 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AA_Uzs3r57pUp_0QITWxiKTUFX6seektks5uyO7ugaJpZM4YxKzF

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441350680, or mute the thread https://github.com/notifications/unsubscribe-auth/AA_UzsX3EnCJT5u355M_o5fgYybBJWjMks5uyPv9gaJpZM4YxKzF .

[BigVulcanDeal]

Thanks for the upload .. the file appears to be identical, and gave an identical result (i.e. it threw an error when trying to load the network into the NCS).

And I fat-fingered the previous e-mail .. basically was venting that the NCS 2 "as is" can only be used with OpenVINO, and so it appears to be impossible to access the newer NCS on any machine that's inexpensive enough to be properly considered an "edge" host .. so not really an "edge" solution, which kind of defeats the purpose.

Thanks again,

On Sat, Nov 24, 2018 at 2:28 PM Michael Hogan mike@bareedge.ai wrote:

Thanks for the upload!

OpenVINO is easy .. on an Intel platform. It's just not so easy to host on a y device that is cheap enough to be considered an and it's not very "open", really.

On Sat, Nov 24, 2018, 2:57 AM Donna <notifications@github.com wrote:

OK, it’s uploading, it says 3hrs left, LOL. Crazy

That openvino looks interesting, they sure make it look easy in their quick start guide !

From: BigVulcanDeal Sent: Friday, November 23, 2018 11:33 PM To: donnaware/movidius_windows Cc: Donna; Comment Subject: Re: [donnaware/movidius_windows] The graph file does not seem to behere (#4)

I changed the folder to allow anyone with the link to write. If your graph doesn't work on my system, then I know it's something other than 'old NCSDK vs new NCSDK"

I think the original NCS modules work fine with the RPi, and they should work even better with the new Pi 3 B+, since it has USB 3.0 ..

The OpenVINO stuff is clever, in theory, but it's really complex compared to the old ncsdk. It basically takes an intermediate graph representation and then can compile it for a number of targets. With access to the source code, it would not be hard to break that into two parts .. one part runs on the dev system and produces an NCS binary graph that can be uploaded and the other part is a bit like your sample app .. it sets up the NCS, uploads the binary graph, and then shovels images in and grabs results.

On Sat, Nov 24, 2018, 2:02 AM Donna <notifications@github.com wrote:

Oh, well I could drop my graph file into that google drive if you want.

It could be I was using an older version, I was messing with this a while back but am on another project right now.

When you say you are trying to get a Pi to with NCS2, do you mean a Raspberry Pi board ? Because I was Thinking about that too, that would be fun.

Intel stuff is not always supported all that well I have noticed. The Myriad chips are really cool but it is difficult to get it to work on different platforms. My project was to get it to work on a Lattepanda board which I accomplished. It seems like it might be easier to get it to work on a Linux board tho, like the RPI

Sorry I cannot be of more help.

From: BigVulcanDeal Sent: Friday, November 23, 2018 10:49 PM To: donnaware/movidius_windows Cc: Donna; Comment Subject: Re: [donnaware/movidius_windows] The graph file does not seem to behere (#4)

I did do that, by building the AlexNet example under ncsdk/examples/caffe/AlexNet/ .. but for the NCSDK2 branch. Your mvcd file is a tad smaller than the one with the NCSDK 2, so I presume you that you based your example on the older branch (which is on GitHub as the "master" branch of the ncsdk),

In any case, I certainly don't expect you to take the time to test it to see if it works with your stuff, but .. just in case you are bored, here's a link to a Google Drive folder with the graph file in it. I built it on a Ubuntu VM, from the NCSDK 2.

https://drive.google.com/drive/folders/1-CgduNbh9-WhrOEpz8hkaIkaeuP_jzeL

Or I can maybe build the whole app, including a static version of the DLL so that it's easy to debug, but it's kind of a pain in the neck .. I guess I could install CodeBlocks or something like that. But what I'm really trying to do get a Pi to work with the NCS 2 .. and Intel hasn't released the NCS releant source code for OpenVINO .. so it's frustratingly difficult to figure out how to make this "Edge Device" actually work on edge hardware.

Thanks again for making that example .. very instructive!

On Sat, Nov 24, 2018 at 1:16 AM Donna notifications@github.com wrote:

The graph file is too big for GitHub, it is like 100MB so GitHub wont accept it. Even zipped.

So you have to create it I guess, best way is to do it on an Ubuntu VM, I think it is possible to do on windows but you have to load a lot of stuff to get that to work and it seemed very fiddly. It would be nice if there was an easy way to make the graph file in windows.

Anyhow, I created the graph file using the standard Ubuntu environment and then just copied it over to windows and that works.

Maybe someday someone will find a way to make an exe program to make the graph file or some other simpler way.

From: BigVulcanDeal Sent: Friday, November 23, 2018 2:42 PM To: donnaware/movidius_windows Cc: Subscribed Subject: [donnaware/movidius_windows] The graph file does not seem to be here(#4)

I was unable to find the graph file. I did generate a new AlexNet graph file, but it was on my NCS dev machine, which has the NCSDK2 branch. I get the following when I try to run stuff: ready NCS device found: 3 NCS device Opened. NCS Device opened normally. Graph file loaded. Could not allocate graph for file: graph Error from mvncAllocateGraph is: -10 Thinking that maybe the graph file has firmware dependent I tried the mvcmd file that ships with the NCS2 SDK (it's a little larger, so something about it is different). In any case, basically the same results in the OUTPUT and DEBUG windows. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441346702

, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AA_UzuyQckWXJ-IAUBgLvVc8WZWP3ouSks5uyORIgaJpZM4YxKzF

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441348481 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AA_Uzs3r57pUp_0QITWxiKTUFX6seektks5uyO7ugaJpZM4YxKzF

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441350680, or mute the thread https://github.com/notifications/unsubscribe-auth/AA_UzsX3EnCJT5u355M_o5fgYybBJWjMks5uyPv9gaJpZM4YxKzF .

[donnaware]

Bummer, sucks when stuff does not work the way you are hoping. Ugh.

The thing I was working on was to get it to work on the Lattepanda board which is a Windows 10 SBC. So once I did that I sort of went on to the next gig. But it would be cool to get it to work on an RPI. It seems like it should work. Shrug. Sorry I am not much help.

From: BigVulcanDeal Sent: Saturday, November 24, 2018 3:08 PM To: donnaware/movidius_windows Cc: Donna; Comment Subject: Re: [donnaware/movidius_windows] The graph file does not seem to behere (#4)

Thanks for the upload .. the file appears to be identical, and gave an identical result (i.e. it threw an error when trying to load the network into the NCS).

And I fat-fingered the previous e-mail .. basically was venting that the NCS 2 "as is" can only be used with OpenVINO, and so it appears to be impossible to access the newer NCS on any machine that's inexpensive enough to be properly considered an "edge" host .. so not really an "edge" solution, which kind of defeats the purpose.

Thanks again,

On Sat, Nov 24, 2018 at 2:28 PM Michael Hogan mike@bareedge.ai wrote:

Thanks for the upload!

OpenVINO is easy .. on an Intel platform. It's just not so easy to host on a y device that is cheap enough to be considered an and it's not very "open", really.

On Sat, Nov 24, 2018, 2:57 AM Donna <notifications@github.com wrote:

OK, it’s uploading, it says 3hrs left, LOL. Crazy

That openvino looks interesting, they sure make it look easy in their quick start guide !

From: BigVulcanDeal Sent: Friday, November 23, 2018 11:33 PM To: donnaware/movidius_windows Cc: Donna; Comment Subject: Re: [donnaware/movidius_windows] The graph file does not seem to behere (#4)

I changed the folder to allow anyone with the link to write. If your graph doesn't work on my system, then I know it's something other than 'old NCSDK vs new NCSDK"

I think the original NCS modules work fine with the RPi, and they should work even better with the new Pi 3 B+, since it has USB 3.0 ..

The OpenVINO stuff is clever, in theory, but it's really complex compared to the old ncsdk. It basically takes an intermediate graph representation and then can compile it for a number of targets. With access to the source code, it would not be hard to break that into two parts .. one part runs on the dev system and produces an NCS binary graph that can be uploaded and the other part is a bit like your sample app .. it sets up the NCS, uploads the binary graph, and then shovels images in and grabs results.

On Sat, Nov 24, 2018, 2:02 AM Donna <notifications@github.com wrote:

Oh, well I could drop my graph file into that google drive if you want.

It could be I was using an older version, I was messing with this a while back but am on another project right now.

When you say you are trying to get a Pi to with NCS2, do you mean a Raspberry Pi board ? Because I was Thinking about that too, that would be fun.

Intel stuff is not always supported all that well I have noticed. The Myriad chips are really cool but it is difficult to get it to work on different platforms. My project was to get it to work on a Lattepanda board which I accomplished. It seems like it might be easier to get it to work on a Linux board tho, like the RPI

Sorry I cannot be of more help.

From: BigVulcanDeal Sent: Friday, November 23, 2018 10:49 PM To: donnaware/movidius_windows Cc: Donna; Comment Subject: Re: [donnaware/movidius_windows] The graph file does not seem to behere (#4)

I did do that, by building the AlexNet example under ncsdk/examples/caffe/AlexNet/ .. but for the NCSDK2 branch. Your mvcd file is a tad smaller than the one with the NCSDK 2, so I presume you that you based your example on the older branch (which is on GitHub as the "master" branch of the ncsdk),

In any case, I certainly don't expect you to take the time to test it to see if it works with your stuff, but .. just in case you are bored, here's a link to a Google Drive folder with the graph file in it. I built it on a Ubuntu VM, from the NCSDK 2.

https://drive.google.com/drive/folders/1-CgduNbh9-WhrOEpz8hkaIkaeuP_jzeL

Or I can maybe build the whole app, including a static version of the DLL so that it's easy to debug, but it's kind of a pain in the neck .. I guess I could install CodeBlocks or something like that. But what I'm really trying to do get a Pi to work with the NCS 2 .. and Intel hasn't released the NCS releant source code for OpenVINO .. so it's frustratingly difficult to figure out how to make this "Edge Device" actually work on edge hardware.

Thanks again for making that example .. very instructive!

On Sat, Nov 24, 2018 at 1:16 AM Donna notifications@github.com wrote:

The graph file is too big for GitHub, it is like 100MB so GitHub wont accept it. Even zipped.

So you have to create it I guess, best way is to do it on an Ubuntu VM, I think it is possible to do on windows but you have to load a lot of stuff to get that to work and it seemed very fiddly. It would be nice if there was an easy way to make the graph file in windows.

Anyhow, I created the graph file using the standard Ubuntu environment and then just copied it over to windows and that works.

Maybe someday someone will find a way to make an exe program to make the graph file or some other simpler way.

From: BigVulcanDeal Sent: Friday, November 23, 2018 2:42 PM To: donnaware/movidius_windows Cc: Subscribed Subject: [donnaware/movidius_windows] The graph file does not seem to be here(#4)

I was unable to find the graph file. I did generate a new AlexNet graph file, but it was on my NCS dev machine, which has the NCSDK2 branch. I get the following when I try to run stuff: ready NCS device found: 3 NCS device Opened. NCS Device opened normally. Graph file loaded. Could not allocate graph for file: graph Error from mvncAllocateGraph is: -10 Thinking that maybe the graph file has firmware dependent I tried the mvcmd file that ships with the NCS2 SDK (it's a little larger, so something about it is different). In any case, basically the same results in the OUTPUT and DEBUG windows. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441346702

, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AA_UzuyQckWXJ-IAUBgLvVc8WZWP3ouSks5uyORIgaJpZM4YxKzF

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441348481 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AA_Uzs3r57pUp_0QITWxiKTUFX6seektks5uyO7ugaJpZM4YxKzF

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441350680, or mute the thread https://github.com/notifications/unsubscribe-auth/AA_UzsX3EnCJT5u355M_o5fgYybBJWjMks5uyPv9gaJpZM4YxKzF .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[BigVulcanDeal]

It was helpful .. maybe I will pick up a Latte

On Sun, Nov 25, 2018, 7:12 PM Donna <notifications@github.com wrote:

Bummer, sucks when stuff does not work the way you are hoping. Ugh.

The thing I was working on was to get it to work on the Lattepanda board which is a Windows 10 SBC. So once I did that I sort of went on to the next gig. But it would be cool to get it to work on an RPI. It seems like it should work. Shrug. Sorry I am not much help.

From: BigVulcanDeal Sent: Saturday, November 24, 2018 3:08 PM To: donnaware/movidius_windows Cc: Donna; Comment Subject: Re: [donnaware/movidius_windows] The graph file does not seem to behere (#4)

Thanks for the upload .. the file appears to be identical, and gave an identical result (i.e. it threw an error when trying to load the network into the NCS).

And I fat-fingered the previous e-mail .. basically was venting that the NCS 2 "as is" can only be used with OpenVINO, and so it appears to be impossible to access the newer NCS on any machine that's inexpensive enough to be properly considered an "edge" host .. so not really an "edge" solution, which kind of defeats the purpose.

Thanks again,

On Sat, Nov 24, 2018 at 2:28 PM Michael Hogan mike@bareedge.ai wrote:

Thanks for the upload!

OpenVINO is easy .. on an Intel platform. It's just not so easy to host on a y device that is cheap enough to be considered an and it's not very "open", really.

On Sat, Nov 24, 2018, 2:57 AM Donna <notifications@github.com wrote:

OK, it’s uploading, it says 3hrs left, LOL. Crazy

That openvino looks interesting, they sure make it look easy in their quick start guide !

From: BigVulcanDeal Sent: Friday, November 23, 2018 11:33 PM To: donnaware/movidius_windows Cc: Donna; Comment Subject: Re: [donnaware/movidius_windows] The graph file does not seem to behere (#4)

I changed the folder to allow anyone with the link to write. If your graph doesn't work on my system, then I know it's something other than 'old NCSDK vs new NCSDK"

I think the original NCS modules work fine with the RPi, and they should work even better with the new Pi 3 B+, since it has USB 3.0 ..

The OpenVINO stuff is clever, in theory, but it's really complex compared to the old ncsdk. It basically takes an intermediate graph representation and then can compile it for a number of targets. With access to the source code, it would not be hard to break that into two parts .. one part runs on the dev system and produces an NCS binary graph that can be uploaded and the other part is a bit like your sample app .. it sets up the NCS, uploads the binary graph, and then shovels images in and grabs results.

On Sat, Nov 24, 2018, 2:02 AM Donna <notifications@github.com wrote:

Oh, well I could drop my graph file into that google drive if you want.

It could be I was using an older version, I was messing with this a while back but am on another project right now.

When you say you are trying to get a Pi to with NCS2, do you mean a Raspberry Pi board ? Because I was Thinking about that too, that would be fun.

Intel stuff is not always supported all that well I have noticed. The Myriad chips are really cool but it is difficult to get it to work on different platforms. My project was to get it to work on a Lattepanda board which I accomplished. It seems like it might be easier to get it to work on a Linux board tho, like the RPI

Sorry I cannot be of more help.

From: BigVulcanDeal Sent: Friday, November 23, 2018 10:49 PM To: donnaware/movidius_windows Cc: Donna; Comment Subject: Re: [donnaware/movidius_windows] The graph file does not seem to behere (#4)

I did do that, by building the AlexNet example under ncsdk/examples/caffe/AlexNet/ .. but for the NCSDK2 branch. Your mvcd file is a tad smaller than the one with the NCSDK 2, so I presume you that you based your example on the older branch (which is on GitHub as the "master" branch of the ncsdk),

In any case, I certainly don't expect you to take the time to test it to see if it works with your stuff, but .. just in case you are bored, here's a link to a Google Drive folder with the graph file in it. I built it on a Ubuntu VM, from the NCSDK 2.

https://drive.google.com/drive/folders/1-CgduNbh9-WhrOEpz8hkaIkaeuP_jzeL

Or I can maybe build the whole app, including a static version of the DLL so that it's easy to debug, but it's kind of a pain in the neck .. I guess I could install CodeBlocks or something like that. But what I'm really trying to do get a Pi to work with the NCS 2 .. and Intel hasn't released the NCS releant source code for OpenVINO .. so it's frustratingly difficult to figure out how to make this "Edge Device" actually work on edge hardware.

Thanks again for making that example .. very instructive!

On Sat, Nov 24, 2018 at 1:16 AM Donna notifications@github.com wrote:

The graph file is too big for GitHub, it is like 100MB so GitHub wont accept it. Even zipped.

So you have to create it I guess, best way is to do it on an Ubuntu VM, I think it is possible to do on windows but you have to load a lot of stuff to get that to work and it seemed very fiddly. It would be nice if there was an easy way to make the graph file in windows.

Anyhow, I created the graph file using the standard Ubuntu environment and then just copied it over to windows and that works.

Maybe someday someone will find a way to make an exe program to make the graph file or some other simpler way.

From: BigVulcanDeal Sent: Friday, November 23, 2018 2:42 PM To: donnaware/movidius_windows Cc: Subscribed Subject: [donnaware/movidius_windows] The graph file does not seem to be here(#4)

I was unable to find the graph file. I did generate a new AlexNet graph file, but it was on my NCS dev machine, which has the NCSDK2 branch. I get the following when I try to run stuff: ready NCS device found: 3 NCS device Opened. NCS Device opened normally. Graph file loaded. Could not allocate graph for file: graph Error from mvncAllocateGraph is: -10 Thinking that maybe the graph file has firmware dependent I tried the mvcmd file that ships with the NCS2 SDK (it's a little larger, so something about it is different). In any case, basically the same results in the OUTPUT and DEBUG windows. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441346702

, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AA_UzuyQckWXJ-IAUBgLvVc8WZWP3ouSks5uyORIgaJpZM4YxKzF

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441348481

, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AA_Uzs3r57pUp_0QITWxiKTUFX6seektks5uyO7ugaJpZM4YxKzF

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441350680 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AA_UzsX3EnCJT5u355M_o5fgYybBJWjMks5uyPv9gaJpZM4YxKzF

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441486817, or mute the thread https://github.com/notifications/unsubscribe-auth/AA_UziZkikb1sN54s87AG5OmHRBf5jd-ks5uyzHtgaJpZM4YxKzF .

[donnaware]

Oh, I am not touting the Lattepanda, it was just that someone was willing to pay to get the movidius dealier to work on it.’

I think a cool application would be like a Ring doorbell type thing where it would recognize who is at the door so it would tell you who is at your door if it is someone you know instead of just that there is a stranger at your door, then you have to connect to it etc. which usually is very slow etc.

Anyhow, I thing there are cool edge application for it, but you are right that they are not making it very easy.

I am not sure what to say, it is a cool chip, they would be smart to support it better I think. You are right, edge applications seem like the right fit.

Shrug. We will see I guess.

From: BigVulcanDeal Sent: Sunday, November 25, 2018 5:05 PM To: donnaware/movidius_windows Cc: Donna; Comment Subject: Re: [donnaware/movidius_windows] The graph file does not seem to behere (#4)

It was helpful .. maybe I will pick up a Latte

On Sun, Nov 25, 2018, 7:12 PM Donna <notifications@github.com wrote:

Bummer, sucks when stuff does not work the way you are hoping. Ugh.

The thing I was working on was to get it to work on the Lattepanda board which is a Windows 10 SBC. So once I did that I sort of went on to the next gig. But it would be cool to get it to work on an RPI. It seems like it should work. Shrug. Sorry I am not much help.

From: BigVulcanDeal Sent: Saturday, November 24, 2018 3:08 PM To: donnaware/movidius_windows Cc: Donna; Comment Subject: Re: [donnaware/movidius_windows] The graph file does not seem to behere (#4)

Thanks for the upload .. the file appears to be identical, and gave an identical result (i.e. it threw an error when trying to load the network into the NCS).

And I fat-fingered the previous e-mail .. basically was venting that the NCS 2 "as is" can only be used with OpenVINO, and so it appears to be impossible to access the newer NCS on any machine that's inexpensive enough to be properly considered an "edge" host .. so not really an "edge" solution, which kind of defeats the purpose.

Thanks again,

On Sat, Nov 24, 2018 at 2:28 PM Michael Hogan mike@bareedge.ai wrote:

Thanks for the upload!

OpenVINO is easy .. on an Intel platform. It's just not so easy to host on a y device that is cheap enough to be considered an and it's not very "open", really.

On Sat, Nov 24, 2018, 2:57 AM Donna <notifications@github.com wrote:

OK, it’s uploading, it says 3hrs left, LOL. Crazy

That openvino looks interesting, they sure make it look easy in their quick start guide !

From: BigVulcanDeal Sent: Friday, November 23, 2018 11:33 PM To: donnaware/movidius_windows Cc: Donna; Comment Subject: Re: [donnaware/movidius_windows] The graph file does not seem to behere (#4)

I changed the folder to allow anyone with the link to write. If your graph doesn't work on my system, then I know it's something other than 'old NCSDK vs new NCSDK"

I think the original NCS modules work fine with the RPi, and they should work even better with the new Pi 3 B+, since it has USB 3.0 ..

The OpenVINO stuff is clever, in theory, but it's really complex compared to the old ncsdk. It basically takes an intermediate graph representation and then can compile it for a number of targets. With access to the source code, it would not be hard to break that into two parts .. one part runs on the dev system and produces an NCS binary graph that can be uploaded and the other part is a bit like your sample app .. it sets up the NCS, uploads the binary graph, and then shovels images in and grabs results.

On Sat, Nov 24, 2018, 2:02 AM Donna <notifications@github.com wrote:

Oh, well I could drop my graph file into that google drive if you want.

It could be I was using an older version, I was messing with this a while back but am on another project right now.

When you say you are trying to get a Pi to with NCS2, do you mean a Raspberry Pi board ? Because I was Thinking about that too, that would be fun.

Intel stuff is not always supported all that well I have noticed. The Myriad chips are really cool but it is difficult to get it to work on different platforms. My project was to get it to work on a Lattepanda board which I accomplished. It seems like it might be easier to get it to work on a Linux board tho, like the RPI

Sorry I cannot be of more help.

From: BigVulcanDeal Sent: Friday, November 23, 2018 10:49 PM To: donnaware/movidius_windows Cc: Donna; Comment Subject: Re: [donnaware/movidius_windows] The graph file does not seem to behere (#4)

I did do that, by building the AlexNet example under ncsdk/examples/caffe/AlexNet/ .. but for the NCSDK2 branch. Your mvcd file is a tad smaller than the one with the NCSDK 2, so I presume you that you based your example on the older branch (which is on GitHub as the "master" branch of the ncsdk),

In any case, I certainly don't expect you to take the time to test it to see if it works with your stuff, but .. just in case you are bored, here's a link to a Google Drive folder with the graph file in it. I built it on a Ubuntu VM, from the NCSDK 2.

https://drive.google.com/drive/folders/1-CgduNbh9-WhrOEpz8hkaIkaeuP_jzeL

Or I can maybe build the whole app, including a static version of the DLL so that it's easy to debug, but it's kind of a pain in the neck .. I guess I could install CodeBlocks or something like that. But what I'm really trying to do get a Pi to work with the NCS 2 .. and Intel hasn't released the NCS releant source code for OpenVINO .. so it's frustratingly difficult to figure out how to make this "Edge Device" actually work on edge hardware.

Thanks again for making that example .. very instructive!

On Sat, Nov 24, 2018 at 1:16 AM Donna notifications@github.com wrote:

The graph file is too big for GitHub, it is like 100MB so GitHub wont accept it. Even zipped.

So you have to create it I guess, best way is to do it on an Ubuntu VM, I think it is possible to do on windows but you have to load a lot of stuff to get that to work and it seemed very fiddly. It would be nice if there was an easy way to make the graph file in windows.

Anyhow, I created the graph file using the standard Ubuntu environment and then just copied it over to windows and that works.

Maybe someday someone will find a way to make an exe program to make the graph file or some other simpler way.

From: BigVulcanDeal Sent: Friday, November 23, 2018 2:42 PM To: donnaware/movidius_windows Cc: Subscribed Subject: [donnaware/movidius_windows] The graph file does not seem to be here(#4)

I was unable to find the graph file. I did generate a new AlexNet graph file, but it was on my NCS dev machine, which has the NCSDK2 branch. I get the following when I try to run stuff: ready NCS device found: 3 NCS device Opened. NCS Device opened normally. Graph file loaded. Could not allocate graph for file: graph Error from mvncAllocateGraph is: -10 Thinking that maybe the graph file has firmware dependent I tried the mvcmd file that ships with the NCS2 SDK (it's a little larger, so something about it is different). In any case, basically the same results in the OUTPUT and DEBUG windows. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441346702

, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AA_UzuyQckWXJ-IAUBgLvVc8WZWP3ouSks5uyORIgaJpZM4YxKzF

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441348481

, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AA_Uzs3r57pUp_0QITWxiKTUFX6seektks5uyO7ugaJpZM4YxKzF

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441350680 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AA_UzsX3EnCJT5u355M_o5fgYybBJWjMks5uyPv9gaJpZM4YxKzF

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/donnaware/movidius_windows/issues/4#issuecomment-441486817, or mute the thread https://github.com/notifications/unsubscribe-auth/AA_UziZkikb1sN54s87AG5OmHRBf5jd-ks5uyzHtgaJpZM4YxKzF .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.