Visweb - Revision history

Hua Guo: /* Removing VisWeb Pubs */

2014-01-17T21:41:26Z

Removing VisWeb Pubs

← Older revision		Revision as of 21:41, 17 January 2014
Line 86:		Line 86:

	Then it's probably because the key of the entry you are trying to remove has not been removed from the author's page in the people directory and therefore caused a dependency problem. To fix the problem,		Then it's probably because the key of the entry you are trying to remove has not been removed from the author's page in the people directory and therefore caused a dependency problem. To fix the problem,
	* EDIT <person>.txt file inside the visweb/people directory for each co-author on the paper to remove the ~~bad~~ key		* EDIT <person>.txt file inside the visweb/people directory for each co-author on the paper to remove the key of the paper that you are trying to remove
	* RUN viswebupdate		* RUN viswebupdate

Hua Guo: /* Removing VisWeb Pubs */

2014-01-17T21:39:59Z

Removing VisWeb Pubs

← Older revision		Revision as of 21:39, 17 January 2014
Line 85:		Line 85:
	Terminated		Terminated

	Then it's probably because the key of the entry you are trying to remove has not been removed from the author's page in the people directory and therefore caused a problem. To fix the problem,		Then it's probably because the key of the entry you are trying to remove has not been removed from the author's page in the people directory and therefore caused a dependency problem. To fix the problem,
	* EDIT <person>.txt file inside the visweb/people directory for each co-author on the paper to remove the bad key		* EDIT <person>.txt file inside the visweb/people directory for each co-author on the paper to remove the bad key
	* RUN viswebupdate		* RUN viswebupdate

Hua Guo: /* Removing VisWeb Pubs */

2014-01-17T21:39:10Z

Removing VisWeb Pubs

← Older revision		Revision as of 21:39, 17 January 2014
Line 85:		Line 85:
	Terminated		Terminated

	Then it's probably because the entry you are trying to remove has not been removed from the author's page in the people directory and therefore caused a problem. To fix the problem,		Then it's probably because the key of the entry you are trying to remove has not been removed from the author's page in the people directory and therefore caused a problem. To fix the problem,
	* EDIT <person>.txt file inside the visweb/people directory for each co-author on the paper to remove the bad key		* EDIT <person>.txt file inside the visweb/people directory for each co-author on the paper to remove the bad key
	* RUN viswebupdate		* RUN viswebupdate

Hua Guo: /* Removing VisWeb Pubs */

2014-01-17T21:38:38Z

Removing VisWeb Pubs

Hua Guo: /* Removing VisWeb Pubs */

2014-01-17T21:37:25Z

Removing VisWeb Pubs

@@ Line 69: / Line 69: @@
 * RUN viswebupdate
-If you follow the step above but still get an error
+Update on Jan.17, 2014:
 === Common Questions ===

Hua Guo: /* Removing VisWeb Pubs */

2014-01-17T21:27:02Z

Removing VisWeb Pubs

← Older revision		Revision as of 21:27, 17 January 2014
Line 68:		Line 68:
	* COPY visweb/pubs/$entry to /pro/web/web/research/vis/input/changed/remove		* COPY visweb/pubs/$entry to /pro/web/web/research/vis/input/changed/remove
	* RUN viswebupdate		* RUN viswebupdate

			If you follow the step above but still get an error

	=== Common Questions ===		=== Common Questions ===

Ryan Cabeen at 22:10, 7 June 2013

2013-06-07T22:10:52Z

← Older revision		Revision as of 22:10, 7 June 2013
Line 76:		Line 76:
	''I just changed my name and ran viswebupdate, but it isn't reflected in the list...''		''I just changed my name and ran viswebupdate, but it isn't reflected in the list...''
	* Try using 'touch' on your publication entries in the pubs directory. viswebupdate will not re-render publications whose timestamps have not changed since the last update.		* Try using 'touch' on your publication entries in the pubs directory. viswebupdate will not re-render publications whose timestamps have not changed since the last update.

			''I added a pdf for a publication, but it isn't reflected in the list...''
			* See the above solution

	''Why aren't my publications linked to my user page?''		''Why aren't my publications linked to my user page?''

Ryan Cabeen at 18:34, 3 April 2012

2012-04-03T18:34:36Z

← Older revision		Revision as of 18:34, 3 April 2012
Line 62:		Line 62:
	* EDIT the file directly in /pubs/ or /bib/		* EDIT the file directly in /pubs/ or /bib/
	* RUN viswebupdate normally.		* RUN viswebupdate normally.

			''In case you used the deprecated web interface to remove an entry and consequently break visweb:''
			* COPY an existing and valid entry to visweb/pubs/$entry
			* RUN viswebupdate
			* COPY visweb/pubs/$entry to /pro/web/web/research/vis/input/changed/remove
			* RUN viswebupdate

	=== Common Questions ===		=== Common Questions ===

Steven Gomez: /* Updating the Website */

2012-03-04T19:59:45Z

Updating the Website

@@ Line 48: / Line 48: @@
 * Entities are stored in '''/research/graphics/common/visweb/''' and can also be reached through the link '''/pro/graphics/visweb/'''.  Look for the subdirectory corresponding to the type of entity you want to add/change.
 * The update script lives at '''/research/graphics/tools/visweb/bin/viswebupdate.sh''' and can also be reached through the link at '''/research/graphics/tools/linux/bin/viswebupdate'''.
 === Common Questions ===
@@ Line 59: / Line 73: @@
 ''Why aren't my publications linked to my user page?''
 * The publication entry might have listed your full name as an author instead of using $yourlogin.  You must use $yourlogin in the authors field in order for VisWeb and viswebupdate to associate it with your page.
 == VisWeb Software ==

Steven Gomez: /* via the CS File System */

2011-11-19T00:11:29Z

via the CS File System

← Older revision		Revision as of 00:11, 19 November 2011
Line 47:		Line 47:
	For reference:		For reference:
	* Entities are stored in '''/research/graphics/common/visweb/''' and can also be reached through the link '''/pro/graphics/visweb/'''. Look for the subdirectory corresponding to the type of entity you want to add/change.		* Entities are stored in '''/research/graphics/common/visweb/''' and can also be reached through the link '''/pro/graphics/visweb/'''. Look for the subdirectory corresponding to the type of entity you want to add/change.
	* The update script lives at '''/research/graphics/tools/visweb/bin/viswebupdate.sh'' and can also be reached through the link at '''/research/graphics/tools/linux/bin/viswebupdate'''.		* The update script lives at '''/research/graphics/tools/visweb/bin/viswebupdate.sh''' and can also be reached through the link at '''/research/graphics/tools/linux/bin/viswebupdate'''.

	=== Common Questions ===		=== Common Questions ===

← Older revision		Revision as of 21:38, 17 January 2014
Line 69:		Line 69:
	* RUN viswebupdate		* RUN viswebupdate

	Update on Jan.17, 2014:		'''Update on Jan.17, 2014:'''

	If you have copied an old file to /pro/web/web/research/vis/input/changed/remove/ and run viswebupdate to remove the file, but encounter an error similar to the following;		If you have copied an old file to /pro/web/web/research/vis/input/changed/remove/ and run viswebupdate to remove the file, but encounter an error similar to the following;

	---- Contents of STDERR channel: ---------		---- Contents of STDERR channel: ---------
	/map/gfx0/common/visweb/pubs/Author-2014-ABC: No such file or directory		/map/gfx0/common/visweb/pubs/Author-2014-ABC: No such file or directory
	/map/gfx0/common/visweb/pubs/Author-2014-ABC: No such file or directory		/map/gfx0/common/visweb/pubs/Author-2014-ABC: No such file or directory
	------------------------------------------		------------------------------------------
	** WML:Break: Error in Pass 3 (rc=1).		** WML:Break: Error in Pass 3 (rc=1).
	make[1]: *** [organization/people/author.html] Error 1		make[1]: *** [organization/people/author.html] Error 1
	make[1]: Leaving directory `/gpfs/main/authen/sys/web/cs/web/research/vis'		make[1]: Leaving directory `/gpfs/main/authen/sys/web/cs/web/research/vis'
	make: *** wait: No child processes. Stop.		make: *** wait: No child processes. Stop.
	make: *** Waiting for unfinished jobs....		make: *** Waiting for unfinished jobs....
	make: *** wait: No child processes. Stop.		make: *** wait: No child processes. Stop.
	Terminated		Terminated

	Then it's probably because the entry you are trying to remove has not been removed from the author's page in the people directory and therefore caused a problem. To fix the problem,		Then it's probably because the entry you are trying to remove has not been removed from the author's page in the people directory and therefore caused a problem. To fix the problem,