Analysis of PLM Software Conflict Resolution - Revision history

Marcin: /* Feedback */

2019-08-06T14:51:43Z

Feedback

@@ Line 61: / Line 61: @@
 =Feedback=
 ==[[Yorik]]==
 Hi Marcin,

Marcin: /* Existing */

2019-07-27T17:43:15Z

Existing

← Older revision		Revision as of 17:43, 27 July 2019
Line 19:		Line 19:
	==Existing==		==Existing==
	#Break down machines according to [[Module Based Design]], and save components as small as possible.		#Break down machines according to [[Module Based Design]], and save components as small as possible.
	#Lock in admissible parts by merging them into official repository. Delete redundant parts. Needs a strong manager + cooperation of community via ~~Annnotated~~ History (see [[Incentive Challenge Judging Criteria]]).		#Lock in admissible parts by merging them into official repository. Delete redundant parts. Needs a strong manager + cooperation of community via [[Annotated Visual History]] (see [[Incentive Challenge Judging Criteria]]).
	#Create containers that load the individual components - as FreeCAD [[a2+ Workbench]].		#Create containers that load the individual components - as FreeCAD [[a2+ Workbench]].
	#Reduce the size of the container to only file names		#Reduce the size of the container to only file names

Marcin: /* Current Solution */

2019-07-27T17:41:13Z

Current Solution

← Older revision		Revision as of 17:41, 27 July 2019
Line 16:		Line 16:

	=Current Solution=		=Current Solution=

			==Existing==
	#Break down machines according to [[Module Based Design]], and save components as small as possible.		#Break down machines according to [[Module Based Design]], and save components as small as possible.
	#Create containers that load the individual components - as FreeCAD [[a2+ Workbench]]		#Lock in admissible parts by merging them into official repository. Delete redundant parts. Needs a strong manager + cooperation of community via Annnotated History (see [[Incentive Challenge Judging Criteria]]).
			#Create containers that load the individual components - as FreeCAD [[a2+ Workbench]].
			#Reduce the size of the container to only file names

	=Problem Statement=		=Problem Statement=

Marcin: /* Question */

2019-07-27T17:24:54Z

Question

← Older revision		Revision as of 17:24, 27 July 2019
Line 14:		Line 14:

	What are your thoughts?		What are your thoughts?

			=Current Solution=
			#Break down machines according to [[Module Based Design]], and save components as small as possible.
			#Create containers that load the individual components - as FreeCAD [[a2+ Workbench]]

	=Problem Statement=		=Problem Statement=

Marcin at 17:21, 27 July 2019

2019-07-27T17:21:54Z

← Older revision		Revision as of 17:21, 27 July 2019
Line 51:		Line 51:
	*[[CAD PLM]]		*[[CAD PLM]]
	*[[Home made PLM project]]		*[[Home made PLM project]]

			=Feedback=
			==[[Yorik]]==
			Hi Marcin,

			Hmm complex problem, lots of people discussing and argueing about it since long...

			My two cents:

			True real-time collaboration requires a complex, dedicated protocol where each and every "move" is registered. The only I know of was something developed by Eskil Steenberg for Blender (and an online game he did called "love") called Verse. It kind of worked. But there is a huge amount of data to be transmitted, so it failed quite easily. But you could really see other people push the vertices in real time...

			While this is good for playing and "rough 3D sketching", it's not that interesting for more accurate design. Changes are so fast and so many that the "changes stack", or model history, becomes absurdly complex, and therefore unuseful. Also, speaking of experience, comparing working with dropbox-like solutions where each file save gets recorded, with working with git-like solutions, where commits are a decision of the user, with a meaningful message and a chosen set of file, I wouldn't hesitate one second to say the latter is far more interesting. There is an abysmal difference in the control you can have over the whole design, who did what, when and why, and just by reading the git log you get a fairly good idea of the whole design process.

			I would say something like this: Reviewing 3D files together, in real-time, maybe with the ability to mark or annotate them, would be tremendously useful. Modeling and committing changes to the model, however, should be a more carefully thought and undertaken process, with better control over each "step", what each of these steps contains being something that is decided by the designer, and not by an automated system.

			The way git handles binary files like FreeCAD files is indeed an issue. FreeCAD files are actually zip files, so they are handled as a binary blob by git. Meaning, on each commit the whole file is stored again. If you commit ten times a 10Mb file, your git folder stores 100Mb.

			This is very common as soon as you start working with non-text files. Even if the file format is text-based instead of binary, more than often, a simple change in a 3D file (moving a piece 10mm) creates many changes spread all over the file.

			Speaking strictly about FreeCAD (but it might apply to other formats too), there are however several possible paths to attack this:

			1) if you unzip a FreeCAD file, 90% of its contents is text. There are many projects out there whose purpose is to unzip files when committing to git, and rezip after pulling: https://forum.freecadweb.org/viewtopic.php?f=22&t=8688&start=20 This could help reducing drammatically the size of a git repo containing FreeCAD files (if you move a piece by 10mm, only a pretty small fraction of the file will change) but it will still be hard to get a human-readable summary of what has changed, which is another big advantage of working with git.

			2) I started working some time ago on a small script ( https://github.com/FreeCAD/FreeCAD/blob/master/src/Tools/fcinfo ) whose purpose is to print a "text representation" of a FreeCAD file. The idea is that you could use this script to produce human-understandable diffs between two FreeCAD files (ex: object "Piece" was at x=10mm in the old file, now it is at x=20mm). Git allows you all kind of tricks to use your own diff programs for specific filetypes.

			Basically this won't solve the main problem of "what ahppens when two people commit to the same file at the same time". No software I know of is able to work out this kind of problem with binary files. Unzipping a FreeCAD file might allow to do partial merge, though. But this needs some heavy testing, an will fail in many cases. The .brep files, for example, that store the shape of each file, although they are text files, often change drastically with a very simple change in the model, and will probably not be reconciliable/mergeable.

			But even so there are certainly huge progresses to be done, and I believe these zip-based compond formats like FreeCAD's (libroffice uses that system too, and nowadays, would you believe, even microsoft, docx and xlsx are also unzippable) are the best possible compromise between binary formats and text-based formats...

			I'd love to know how this question is going forward on your side, please keep me informed!

Marcin: /* Context */

2019-07-27T17:18:11Z

Context

← Older revision		Revision as of 17:18, 27 July 2019
Line 5:		Line 5:
	==Context==		==Context==

	Question to Yorik, core FreeCAD developer - OSE will launch a $250k [[Incentive Challenge]] on the HeroX platform on September 2020 to build an open source, pro grade 3d printed cordless drill. We expect 1000s of participants.		Question to [[Yorik]], core FreeCAD developer: OSE will launch a $250k [[Incentive Challenge]] on the HeroX platform on September 2020 to build an open source, pro grade 3d printed cordless drill. We expect 1000s of participants.

	Regarding file conflict resolution - can you comment on what I know about this right now - link below - and what Is currently available in FreeCAD? We plan to simply use our wiki for FreeCAD file version history, with Annotated change log pictures uploaded manually to make design changes transparent - allowing thousands of people to contribute to he same design in near real-time.		Regarding file conflict resolution - can you comment on what I know about this right now - link below - and what Is currently available in FreeCAD? We plan to simply use our wiki for FreeCAD file version history, with Annotated change log pictures uploaded manually to make design changes transparent - allowing thousands of people to contribute to he same design in near real-time.

Marcin: /* Context */

2019-07-27T17:17:51Z

Context

← Older revision		Revision as of 17:17, 27 July 2019
Line 5:		Line 5:
	==Context==		==Context==

	OSE will launch a $250k [[Incentive Challenge]] on the HeroX platform on September 2020 to build an open source, pro grade 3d printed cordless drill. We expect 1000s of participants.		Question to Yorik, core FreeCAD developer - OSE will launch a $250k [[Incentive Challenge]] on the HeroX platform on September 2020 to build an open source, pro grade 3d printed cordless drill. We expect 1000s of participants.

	Regarding file conflict resolution - can you comment on what I know about this right now - link below - and what Is currently available in FreeCAD? We plan to simply use our wiki for FreeCAD file version history, with Annotated change log pictures uploaded manually to make design changes transparent - allowing thousands of people to contribute to he same design in near real-time.		Regarding file conflict resolution - can you comment on what I know about this right now - link below - and what Is currently available in FreeCAD? We plan to simply use our wiki for FreeCAD file version history, with Annotated change log pictures uploaded manually to make design changes transparent - allowing thousands of people to contribute to he same design in near real-time.

Marcin: /* Context */

2019-07-27T17:17:12Z

Context

← Older revision		Revision as of 17:17, 27 July 2019
Line 5:		Line 5:
	==Context==		==Context==

	OSE will launch a $250k [[~~Incentve~~ Challenge]] on the HeroX platform on September 2020 to build an open source, pro grade 3d printed cordless drill. We expect 1000s of participants.		OSE will launch a $250k [[Incentive Challenge]] on the HeroX platform on September 2020 to build an open source, pro grade 3d printed cordless drill. We expect 1000s of participants.

	Regarding file conflict resolution - can you comment on what I know about this right now - link below - and what Is currently available in FreeCAD? We plan to simply use our wiki for FreeCAD file version history, with Annotated change log pictures uploaded manually to make design changes transparent - allowing thousands of people to contribute to he same design in near real-time.		Regarding file conflict resolution - can you comment on what I know about this right now - link below - and what Is currently available in FreeCAD? We plan to simply use our wiki for FreeCAD file version history, with Annotated change log pictures uploaded manually to make design changes transparent - allowing thousands of people to contribute to he same design in near real-time.

Marcin at 17:17, 27 July 2019

2019-07-27T17:17:02Z

← Older revision		Revision as of 17:17, 27 July 2019
Line 1:		Line 1:
			=Question=

	How does professional grade [[PLM]] software resolve file conflicts? And how does OSE achieve even higher performance using simple online tools? Here is an assessment of the state of art in each.		How does professional grade [[PLM]] software resolve file conflicts? And how does OSE achieve even higher performance using simple online tools? Here is an assessment of the state of art in each.

			==Context==

			OSE will launch a $250k [[Incentve Challenge]] on the HeroX platform on September 2020 to build an open source, pro grade 3d printed cordless drill. We expect 1000s of participants.

			Regarding file conflict resolution - can you comment on what I know about this right now - link below - and what Is currently available in FreeCAD? We plan to simply use our wiki for FreeCAD file version history, with Annotated change log pictures uploaded manually to make design changes transparent - allowing thousands of people to contribute to he same design in near real-time.

			See

			https://wiki.opensourceecology.org/wiki/Analysis_of_PLM_Software_Conflict_Resolution#Problem_Statement

			What are your thoughts?

	=Problem Statement=		=Problem Statement=

AbeAnderson: /* Related */

2019-07-24T22:40:55Z

← Older revision		Revision as of 22:40, 24 July 2019
Line 35:		Line 35:

	=Related=		=Related=
	[[CAD PLM]]		*[[CAD PLM]]
	[[Home made PLM project]]		*[[Home made PLM project]]