Pilot Archive
Thread: SpaceLoot.com: now with streaming chat
Raja_Asenn wrote:
I had an idea for how to accelerate and improve the component submission process.
I could enable users to mass-upload component screenshots to the server via a highly automated FTP process. Behind the scenes the system would slurp those uploads into a database. Once processed, logged-in users would see 'pending components (98)' (or however many) and would be able to click the link to bring up a slightly modified component submission form that would include a the screenshot...then it'd just a matter of finger-netting the values into the fields. Both the image submitter and the data entry user would get credit for the submission.
So the question, in two parts:
1) If you don't currently submit data to spaceLoot but doprocess a lot of items in the game, would you be willing to occasionally mass-screenshot and upload those items?
2)as a site user, would you be willing to input data from screenshots from time to time?
I've set a goal of 50,000 components to consider the database to be really robust, and I'm just trying to think of more ways to get us there with the least hassle possible.
yes it would be much easier to just submit SS's instead of having to look at all my SS"s and input all the data... oh and it won't let me veiw the ship registry anymore it says......
15pt verdana; COLOR: black">Element RECORDCOUNT is undefined in QSHIPINTERESTSELECT. The error occurred in D:\Inetpub\wwwroot\starcraft\ship\dsp_MoreInfoFooter.cfm: line 13
Called from D:\Inetpub\wwwroot\starcraft\ship\dsp_View.cfm: line 909
Called from D:\Inetpub\wwwroot\starcraft\ship\dsp_View.cfm: line 723
Called from D:\Inetpub\wwwroot\starcraft\ship\dsp_View.cfm: line 1
Called from D:\Inetpub\wwwroot\starcraft\ship\index.cfm: line 21
Called from D:\Inetpub\wwwroot\starcraft\index.cfm: line 53
11 : --->
12 :
13 : <cfif qShipInterestSelect.recordcount>
14 : <cfset variables.sNotificationWord = "On">
15 : <cfelse>
at cfdsp_MoreInfoFooter2ecfm1746545760.runPage(D:\Inetpub\wwwroot\starcraft\ship\dsp_MoreInfoFooter.cfm:13) at cfdsp_View2ecfm501626052._factor17(D:\Inetpub\wwwroot\starcraft\ship\dsp_View.cfm:909) at cfdsp_View2ecfm501626052._factor28(D:\Inetpub\wwwroot\starcraft\ship\dsp_View.cfm:723) at cfdsp_View2ecfm501626052.runPage(D:\Inetpub\wwwroot\starcraft\ship\dsp_View.cfm:1) at cfindex2ecfm197263478.runPage(D:\Inetpub\wwwroot\starcraft\ship\index.cfm:21) at cfindex2ecfm860438218.runPage(D:\Inetpub\wwwroot\starcraft\index.cfm:53)
coldfusion.runtime.UndefinedElementException: Element RECORDCOUNT is undefined in QSHIPINTERESTSELECT.
at coldfusion.runtime.CfJspPage.resolveCanonicalName(CfJspPage.java:1049)
at coldfusion.runtime.CfJspPage._resolve(CfJspPage.java:1004)
at coldfusion.runtime.CfJspPage._resolveAndAutoscalarize(CfJspPage.java:1111)
at cfdsp_MoreInfoFooter2ecfm1746545760.runPage(D:\Inetpub\wwwroot\starcraft\ship\dsp_MoreInfoFooter.cfm:13)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:147)
at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:357)
at coldfusion.runtime.CfJspPage._emptyTag(CfJspPage.java:1871)
at cfdsp_View2ecfm501626052._factor17(D:\Inetpub\wwwroot\starcraft\ship\dsp_View.cfm:909)
at cfdsp_View2ecfm501626052._factor28(D:\Inetpub\wwwroot\starcraft\ship\dsp_View.cfm:723)
at cfdsp_View2ecfm501626052.runPage(D:\Inetpub\wwwroot\starcraft\ship\dsp_View.cfm:1)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:147)
at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:357)
at coldfusion.runtime.CfJspPage._emptyTag(CfJspPage.java:1871)
at cfindex2ecfm197263478.runPage(D:\Inetpub\wwwroot\starcraft\ship\index.cfm:21)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:147)
at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:357)
at coldfusion.runtime.CfJspPage._emptyTag(CfJspPage.java:1871)
at cfindex2ecfm860438218.runPage(D:\Inetpub\wwwroot\starcraft\index.cfm:53)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:147)
at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:357)
at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:62)
at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:107)
at coldfusion.filter.PathFilter.invoke(PathFilter.java:80)
at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:47)
at coldfusion.filter.BrowserDebugFilter.invoke(BrowserDebugFilter.java:52)
at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28)
at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:35)
at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:43)
at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)
at coldfusion.CfmServlet.service(CfmServlet.java:105)
at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91)
at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:252)
at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:527)
at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:192)
at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:348)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:451)
at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:294)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
That was a temporary bug related to me being irresponsible and doing dev on the live server. You guys will be seeing that sort of thing from time to time for a while. Shouldn't ever last very long.
Raja_Asenn wrote:
I had an idea for how to accelerate and improve the component submission process.
I could enable users to mass-upload component screenshots to the server via a highly automated FTP process. Behind the scenes the system would slurp those uploads into a database. Once processed, logged-in users would see 'pending components (98)' (or however many) and would be able to click the link to bring up a slightly modified component submission form that would include a the screenshot...then it'd just a matter of finger-netting the values into the fields. Both the image submitter and the data entry user would get credit for the submission.
So the question, in two parts:
1) If you don't currently submit data to spaceLoot but doprocess a lot of items in the game, would you be willing to occasionally mass-screenshot and upload those items?
2)as a site user, would you be willing to input data from screenshots from time to time?
I've set a goal of 50,000 components to consider the database to be really robust, and I'm just trying to think of more ways to get us there with the least hassle possible.
The reason I hold off is exactly that... its apain in the ass to ALT-TAB back and forth. Never though about screenshots though ![]()
How viable is some kind of OCR plugin?
I'm extremely Impressed. I've appreciated the feedback I've received on my ships thus far. Some of it should have been common sense to me as a pilot but nonetheless I am appreciative that it was brought to my attention.
I need to start remembering to do the lootalyzer since I always forget to set up a chat log for it.
idolatry wrote:
The reason I hold off is exactly that... its apain in the ass to ALT-TAB back and forth. Never though about screenshots though
How viable is some kind of OCR plugin?
Kharn wrote:
For the lootalizer, does it notify you or the person submitting the log if there happens to be a component name that is looted that you don't have in the database? Seems like a good place to check for new/previously uncataloged pieces.
Yeah, I added that last week....it's not too fancy, just dumps to a table that only I can check, no GUI for it. Good thing you reminded me, I'm gonna go look at that now....
...holy cow! I've got ten distinct items that aren't matching. fix fix fix
Raja_Asenn wrote:
Kharn wrote:
For the lootalizer, does it notify you or the person submitting the log if there happens to be a component name that is looted that you don't have in the database? Seems like a good place to check for new/previously uncataloged pieces.
Yeah, I added that last week....it's not too fancy, just dumps to a table that only I can check, no GUI for it. Good thing you reminded me, I'm gonna go look at that now....
...holy cow! I've got ten distinct items that aren't matching. fix fix fix
Any way you could print those out in the report on the log? It would be the natural place to put in an interface for unknown components.
done
Kharn wrote:
Any way you could print those out in the report on the log? It would be the natural place to put in an interface for unknown components.
Raja_Asenn wrote:What's under development, in order of likely implementation:- Enhanced lootalyzer data analysis, including side-by-side spawn comparisons- spaceLoot specific discussion forumsThere's a great deal more on my to-do list, just wanted to give you a feel for the direction we're headed over the next few weeks.
I love what I see thus far.
I do have a small request. Would it be possible to add a 90/95/98 percentile to the columns next to standard deviation? I guess I could calculate it from the std dev, but I'd have to re-learn how to do it.
Kharn wrote:
I love what I see thus far.
I do have a small request. Would it be possible to add a 90/95/98 percentile to the columns next to standard deviation? I guess I could calculate it from the std dev, but I'd have to re-learn how to do it.