Welcome to Laser Pointer Forums - discuss green laser pointers, blue laser pointers, and all types of lasers

LPF Donation via Stripe | LPF Donation - Other Methods

Links below open in new window

ArcticMyst Security by Avery

Luminosity - my new LPM data logger project!

Trevor

0
Joined
Jul 17, 2009
Messages
4,386
Points
113
Since the Kenometer uses a freeware graphing software that wasn't actually purpose-built for use with lasers, today I decided that that would be my next LPF-related project.

I've built a basic graphing function, and have started to get things set up to allow for dynamic changes in the scale (the scale changes based on the data received), and have a user-defined logging duration on the X-axis (I haven't yet added labels for this axis).

Here's the first screenshot. I had to just generate random points to graph, since I unfortunately have no Kenometer to develop with.

http://www.safelasers.org/Luminosity/Images/Luminosity.png

My main motivation for posting this thread is simple; I'd like to know what you would like to see in LPM logging software. I have some concepts kicking around in my head, but I'd like to hear what the community can come up with so that I can work it into the software, too.

Cheers.

-Trevor
 
Last edited:





Joined
Dec 30, 2009
Messages
508
Points
18
I think you should be able to label the lines with what laser it is and combine graphs of several lasers to compare peformance.
 

Trevor

0
Joined
Jul 17, 2009
Messages
4,386
Points
113
I think you should be able to label the lines with what laser it is and combine graphs of several lasers to compare peformance.

I'll put the first on my to-do list, but the second is already a feature that's being worked on. :)

-Trevor
 

Kenom

0
Joined
May 4, 2007
Messages
5,629
Points
63
well lets start with the obvious things. The graph must be able to scale automatically if the readings go above what was initially set. Configurable time frames ie 30 seconds 60 seconds or 5 minutes etc. You specify the units. Minutes seconds etc. Poll time should also be changeable so that you can have your data being pulled every second or every 10 seconds.

Being able to change the color associated with a specific line on the graph.
The ability to import another graph and overlay it on the existing graph.
The ability to set your domain in the graph so that you can get rid of data that is not relevant.
Datapoints should have dots on teh poll times so that you can mouse over it and see what that specific datapoint is.

These are all I could think of to begin with. Some of them are pretty common on graphing software, but if your building from the ground up, it's nice to know about them to add them.

I'll come up with more..... :D
 
Joined
May 4, 2009
Messages
5,443
Points
113
this would be alot less hasel to look at if it wasn't so big !


Since the Kenometer uses a freeware graphing software that wasn't actually purpose-built for use with lasers, today I decided that that would be my next LPF-related project.

I've built a basic graphing function, and have started to get things set up to allow for dynamic changes in the scale (the scale changes based on the data received), and have a user-defined logging duration on the X-axis (I haven't yet added labels for this axis).

Here's the first screenshot. I had to just generate random points to graph, since I unfortunately have no Kenometer to develop with.

Luminosity.png


My main motivation for posting this thread is simple; I'd like to know what you would like to see in LPM logging software. I have some concepts kicking around in my head, but I'd like to hear what the community can come up with so that I can work it into the software, too.

Cheers.

-Trevor
 

Trevor

0
Joined
Jul 17, 2009
Messages
4,386
Points
113
this would be alot less hasel to look at if it wasn't so big !

Unquote it and we're golden. :whistle:

well lets start with the obvious things. The graph must be able to scale automatically if the readings go above what was initially set. Configurable time frames ie 30 seconds 60 seconds or 5 minutes etc. You specify the units. Minutes seconds etc. Poll time should also be changeable so that you can have your data being pulled every second or every 10 seconds.

Being able to change the color associated with a specific line on the graph.
The ability to import another graph and overlay it on the existing graph.
The ability to set your domain in the graph so that you can get rid of data that is not relevant.
Datapoints should have dots on teh poll times so that you can mouse over it and see what that specific datapoint is.

These are all I could think of to begin with. Some of them are pretty common on graphing software, but if your building from the ground up, it's nice to know about them to add them.

I'll come up with more..... :D

1. Graph will scale and re-render automatically, that shouldn't be an issue.
2. Configurable timeframe, also not an issue.
3. I can have poll time be configurable, or I can detect it. What is the the Kenometer's standard poll time? Is the USB configurable?
4. Color changing already implemented.
5. I was going to make the utility only start graphing when it detected laser-induced input from the Kenometer, but I could also set a threshold.
6. Already have ideas for a mouseover in the works.

-Trevor
 
Last edited:
Joined
Apr 9, 2008
Messages
374
Points
28
I got the Kenometer, it is great! The software is also great... I am finally sitting down and using it :D

Are you still open for few minor suggestions?
 

Trevor

0
Joined
Jul 17, 2009
Messages
4,386
Points
113
Yep, this is still under active development. What do you have in mind?

I've got a laundry list of things I'm working on. :)

-Trevor
 
Joined
Apr 9, 2008
Messages
374
Points
28
Yep, this is still under active development. What do you have in mind?

I've got a laundry list of things I'm working on. :)

-Trevor

Thanks Trevor. I am glad it is still under development and that your open for suggestions.

Here are some, "just" six of them for now :D:

1. It seems that Luminosity was built for a screen size of 1280x720 (or so), I am using 1024x768, so I can barely read the bottom of Luminosity. Can the Luminosity window be made resizable?

2. The light green font with the white background under “Current Reading” is also barely readable, at least for me.

3. Ken showed me a trick. I am using Windows 7-64bit and I was having problems accessing the Kenometer through Luminosity. He basically said to click Connect-COMx twice, quickly, and then got connected. Is that a bug?

4. Sometimes I need to connect and disconnect a couple of times the Kenometer for Luminosity to recognize that has been connected. I am not sure if it is my system or something with the Kenometer or Luminosity.

5. This may be more complicated to set up: I really like to options to create a new chart, but having to set up the Graphing every time one wants to just see the graphing is time consuming. Sometimes all I want to shine the beam and watch it be graphed. Can it just be set up to have to option to start auto graphing? Something like the chart under “Networking” in the “Windows Task Manager” which has a window that automatically adjusts to the max readout?

6. It would be convenient to not need to disconnect the Kenometer when saving the data, and then connect again to start another graphing, can the program do the disconnect-reconnect automatically, in the background? Same for exiting the application (just the automatic disconnect, not the reconnect :D)

THANKS!
 

Trevor

0
Joined
Jul 17, 2009
Messages
4,386
Points
113
1. It seems that Luminosity was built for a screen size of 1280x720 (or so), I am using 1024x768, so I can barely read the bottom of Luminosity. Can the Luminosity window be made resizable?

This is being addressed in the 2.0 release. I've found an efficient way of allowing live resizing of the graphing area - I hadn't when the initial version was rolling out.

2. The light green font with the white background under “Current Reading” is also barely readable, at least for me.

See this screenshot: http://www.safelasers.org/Luminosity/Images/Luminosity 2010.03.01.01.png

It seems yours is not behaving that way?

3. Ken showed me a trick. I am using Windows 7-64bit and I was having problems accessing the Kenometer through Luminosity. He basically said to click Connect-COMx twice, quickly, and then got connected. Is that a bug?

Yes, I'm working on a different connection method to release a fix.

4. Sometimes I need to connect and disconnect a couple of times the Kenometer for Luminosity to recognize that has been connected. I am not sure if it is my system or something with the Kenometer or Luminosity.

This has to do with the imperfect connection process. Actively working on it for an update to the current release and for the 2.0 release.

5. This may be more complicated to set up: I really like to options to create a new chart, but having to set up the Graphing every time one wants to just see the graphing is time consuming. Sometimes all I want to shine the beam and watch it be graphed. Can it just be set up to have to option to start auto graphing? Something like the chart under “Networking” in the “Windows Task Manager” which has a window that automatically adjusts to the max readout?

There's a live graph in 2.0, which seems like just what you want. :)

6. It would be convenient to not need to disconnect the Kenometer when saving the data, and then connect again to start another graphing, can the program do the disconnect-reconnect automatically, in the background? Same for exiting the application (just the automatic disconnect, not the reconnect :D)

It hadn't occurred to me to just disconnect in the background. The reason for this design was to ensure that two different threads weren't competing for resources at the same time. I'll look into that - it's a good option.

-Trevor
 

Trevor

0
Joined
Jul 17, 2009
Messages
4,386
Points
113
The 2.0 and 3.5 notations are the .NET Framework versions they're targeted for.

When I say a 2.0 release, I'm referring to version 2.0.0.0. Sorry for the ambiguity. :)

Can you upload a screenshot of what you're looking at, per your second suggestion?

-Trevor
 
Joined
Apr 9, 2008
Messages
374
Points
28
The 2.0 and 3.5 notations are the .NET Framework versions they're targeted for.

When I say a 2.0 release, I'm referring to version 2.0.0.0. Sorry for the ambiguity. :)

Can you upload a screenshot of what you're looking at, per your second suggestion?

-Trevor

Here you go:

3302-luminosity.jpg


Here is the "About":

3303-about.jpg


If I am downloading it from the links in the sticky, from Ken's website and using the version on his CD, shouldn't this say 2.0.0 and dated 2010.04.28? Or something like that :D
 




Top